Replacing wireless-communication enabled components in a luminaire

ABSTRACT

A system comprises a plurality of components connected in a wireless network and at least one unconnected (new) component available to join the network. The components are divided amongst a plurality of luminaires, each comprising a respective subgroup of the components including at least one lamp, and each subgroup has a respective subgroup ID. At least a first one of these components is configured to automatically detect whether a previously-present one of the components from the same respective subgroup as the first component is missing from the network. In response to detecting that the previously-present component is missing, the first component automatically causes the new component to be joined to the wireless network, and to be assigned to the same subgroup as the first component under the same subgroup ID.

CROSS-REFERENCE TO PRIOIR APPLICATIONS

This application is the U.S. National Phase application under 35 U.S.C.§ 371 of International Application No. PCT/EP2016/069240, filed on Aug.12, 2016, which claims the benefit of European Patent Application No.1518332.3, filed on Sep. 4, 2015. These applications are herebyincorporated by reference herein.

TECHNICAL FIELD

The present disclosure relates the process of replacing wirelesscommunication enabled lamps and/or other wireless communication enabledcomponents (e.g. sensor or battery) that may be included luminaires.

BACKGROUND

A luminaire (light fixture) is a device comprising at least one lamp foremitting illumination, and any associated socket, support and/orhousing. A luminaire may take any of a variety of forms, such as aconventional ceiling or wall mounted luminaire, free standing luminaireor wall washer, or a less conventional form such as an illuminationsource built into a surface or an item of furniture, or any other typeof lighting device for emitting illumination into an environment. Thelamp refers to an individual light-emitting component within aluminaire, of which there may be one or more per luminaire. The lamp mayalso take any of a number of forms, such as an LED-based lamp, agas-discharge lamp, or a filament bulb. An increasingly popular form oflamp is a retrofittable LED-based lamp comprising one or more LEDs asthe means by which to emit illumination, but being made retrofittableinto a luminaire designed for a traditional filament bulb or fluorescenttube.

A luminaire or even an individual lamp may also be equipped with awireless communication interface allowing the luminaire or lamp to becontrolled remotely by lighting control commands received from a userdevice such as a smartphone, tablet, laptop or desktop computer, orwireless wall-switch; and/or based on sensor readings received from oneor more remote sensors. Nowadays, the communication interface can beincluded directly within the lamp itself (e.g. in the end-cap of aretrofittable replacement for a filament bulb or fluorescent tube). Forexample this can allow a user, through the user device, to turn thelamp's illumination on and off, to dim the illumination level up ordown, to change the colour of the emitted illumination, and/or to createa dynamic (time varying) lighting effect. In one form, the communicationinterface is configured to receive the lighting control commands and/orto share sensor data via a local, short-range radio access technologysuch as Wi-Fi, 802.15.4, ZigBee or Bluetooth. Such lamps may sometimesbe referred to as “connected” lamps.

One type of connected lamp is an instant-fit “tube LED” (TLED) lampwhich retrofits into a luminaire designed for traditional fluorescenttubes. According to the instant-fit TLED approach, the existingfixed-output fluorescent ballast, the TLED lamp-holders and also all theelectrical wiring within the luminaire remain unchanged. Viastraightforward re-lamping, existing “dumb” fluorescent tubes (or even“dumb” TLED tubes) can be exchanged with dimmable connected TLEDs eachhaving an individual, integrated wireless radio.

While LED-based lamps tend to have a longer lifetime than filament bulbsand florescent tubes, nonetheless, for any type of lamp there will berequired a process for replacing a lamp in a luminaire when that lampeventually wears out or breaks, or it is desired to upgrade the lampwith a new model, or such like. For a wirelessly network enabled lamp,this involves not only physically removing the old lamp from the socketof the luminaire and replacing with the new lamp, but also ensuring thenew lamp is connected to the network in a manner that enables it to actas a replacement for the old lamp in terms of its wirelessfunctionality, e.g. to enable it to be controlled in the same way from aremote control unit or app.

U.S. Pat. No. 8,982,754 discloses a system which detects when a node ismissing from a mesh network, and joins a new node to the network toreplace the missing node. However, it does not deal with the issue ofreplacement lamps or other components in luminaires.

SUMMARY

Particularly, nowadays a given luminaire may contain not just a singlewirelessly controlled lamp, but a plurality of such lamps and/or otherwireless communication enabled components (such a sensor that reportsits sensor readings over the wireless network, or a battery that reportsits status over the wireless network). Typically it is desired that thelamps or components of a given luminaire can be addressed bothindividually and as a group (on a per luminaire basis). Thus thecomponents are not just part of a network generally, but are alsodivided into logical subgroups, one per luminaire. I.e. while each suchcomponent may be a unique member of the wireless network with its ownunique network address within the network, thus being individuallyaddressable, typically the wireless components in each luminaire willalso be assigned a respective subgroup ID as well, by which a controllersuch as a remote control unit or app running on a smart phone canaddress all the lamps or all the components of the luminaire as a whole.E.g. this ID may be a ZigBee group address of the ZigBee protocol (“sub”group herein just refers to being a subgroup of the total members of thenetwork). Therefore when replacing a lamp in a luminaire, it is notenough to just to determine that a lamp is missing and needs to bejoined to the network. It is also necessary to determine which luminairethe replacement lamp is to become a member of, i.e. which subgroup ID itshould be joined to. As another example scenario, the grouping of allwireless components housed within the same luminaire aids maintenance;by using the information as to which luminaire a certain wireless asset(e.g. a CO2 sensor) is housed in, this will help to direct themaintenance crew immediately to the right luminaire in the case thatwireless asset needs replacement (instead of searching the brokenasset).

Currently, often the various wireless components in a luminaire do notget grouped at all during commissioning, and hence the maintenance crewhas to physically locate in which luminaire a broken device such as anair quality sensor is foundI Or if sub-grouping is performed (such asfor multiple wireless LED lamps in the same luminaire) then acommissioning technician has to manually check the ID of the luminaire,enter this into a commissioning tool, and assign the new lamp to thesubgroup of the luminaire through the commissioning tool. To verify hisor her work, the technician then stands beneath (or near) the luminairein question and causes it to emit a visible signal (e.g. flash) based onaddressing it via its subgroup ID, then causes the individualreplacement lamp to emit a visible signal (e.g. flash) by addressing itvia its individual network address. If the two signals originate fromthe same luminaire then the technician has got it right, but otherwisehe or she must try again. This is a cumbersome process, especially whenrepeated over many lamps and luminaires in a large re-lamping job or thelike. It would be desirable to provide an improved process to automatethe re-lamping process for wireless communication enabled lamps, or moregenerally the replacement process for wireless communication enabledcomponents in a luminaire.

To address this or other considerations, the present applicationprovides a number of mechanisms by which a remaining lamp or othercomponent in a luminaire can detect the presence of a new wirelesscomponent, and by which the remaining lamp or component can checkwhether a previous one of its companions is still present in the sameluminaire. If a component is missing from the respective luminaire andat the same time a new component appears on the network, it is likelythe new component is a replacement for the missing one. Thus theremaining component that detected this can be configured toautomatically add its new companion to both the network and also the(probably) correct subgroup.

Hence according to one aspect disclosed herein, there is provided asystem comprising a plurality of replaceable components connected in awireless under a collective ID (such as the network ID identifying thenetwork), and at least one unconnected component available to join thenetwork (i.e. at least one new component not yet connected to thenetwork). The components are divided amongst a plurality of luminaires,each respective one of the luminaires comprising a respective subgroupof the components including at least one lamp, and each of the subgroupshaving a respective subgroup ID identifying the respective subgroup. Atleast a first one of the components (e.g. a lamp) is configured toautomatically detects whether a previously-present one of saidcomponents from the same respective one of said subgroups as the firstcomponent (i.e. in the same luminaire) is missing from the network. Inresponse to detecting that the new component is available to join thenetwork, and that the previously-present component is missing from thenetwork, the first component then causes the new component to be joinedto the wireless network under said network ID, and to be assigned to thesame respective subgroup as the first component under the samerespective subgroup ID (e.g. ZigBee group address).

In general the wireless network can be based on any suitable wirelessnetworking protocol such as ZigBee, Wi-Fi, Bluetooth, 802.15.4 orThread. The components may all be lamps, or may be a mixture of lampsand other components such as sensors or batteries.

Preferably, the “first component” in the above method is one of saidplurality of components already connected in the network. I.e. anexisting one of the components detects that one of itspreviously-present neighbours in the same luminaire is missing (which itcan know because it has access to list of previously commissioned lampsor components in its own luminaire, so it can attempt to communicatewith these components and check whether they respond). In this case, thefirst (existing) component is also configured to perform an operation ofdetecting that the unconnected component is available to join thenetwork, and the first component is configured to perform said causingof the unconnected component to join the network in response to thedetection both that the new component is available to join the networkand that the previously present component is missing from the network.

Alternatively however, the “first component” in the above method couldbe the unconnected component (the new component). In this case one ofthe existing components discovers that one of its neighbours is missing(by attempting to communicate with it), then broadcasts this fact in amessage that is detectable by the unconnected (new) component. Hence thenew component detects that one of the other components is missing basedon a message received from an existing component, and then causes itselfto join the network.

Note also that when the method is implemented at the existing component(one of the plurality of components already connected to the network),then the steps of detecting the new component and detecting the missingcomponent can be performed in either order. In some embodiments, the onemay be arranged to trigger the other—i.e. the first component may beconfigured to trigger a check for the missing component in response tothe detection of the new component, or alternatively may be configuredto trigger a check for the new component in response to detecting themissing component. Or as another alternative, both checks could betriggered by a command instigated manually by a user (e.g. through a UIof a commissioning tool or a button on the first lamp or its luminaire).

In embodiments, the first component may be further configured to detectwhether the new component is estimated to be within a predefined spatialproximity of the first component (i.e. according to some predefinedtest); and at least said assigning of the new component to therespective subgroup may be performed on condition of detecting that thenew component is estimated to be within said spatial proximity.

This is particularly advantageous as it allows for replacement ofmultiple components in multiple different luminaires in the samesession. I.e. if the first component detects two (or more) newcomponents available to join the network, it can distinguish which ismost likely to be the replacement for the component missing from its ownluminaire based on a measure of proximity—a component estimated to beclose by is more likely to be the relevant replacement that a componentfar away. A similar existing component in another luminaire alsoperforms the same process to determine that the other new component (orone of the other new components) is the most likely to be thereplacement for its respective missing component, and so forth.

Preferably, said causing of the new component to join the network, bythe first component, is also conditional on the first componentdetecting that the new component is estimated to be within said spatialproximity (the new component may still be caused to join the network byanother of the components elsewhere in one of the other luminaires, butthe fact that it is said first component that does this is conditionalon the test of proximity). However it is not completely excluded thatthe first component could join the new component to the network even ifthe new component is not to be part of the same luminaire).

In embodiments, (according to said predefined test) the first componentmay be configured to perform said detection of whether the new componentis within said spatial proximity by: obtaining an indication of distancebetween the first lamp and the new component based on a measurement ofreceived signal strength or time-of-flight (ToF) of a signal emitted bythe new component, and determining whether the new component isdetermined to be within said spatial proximity based on said indication.E.g. the signal may be a visible light signal, an invisible light signal(infrared or ultraviolet), a radio signal, an audible-range soundsignal, an ultrasound signal, or a heat signal.

For instance this may comprise the first lamp receiving said signal fromthe new component, taking a measurement of received signal strengthand/or time of flight of the signal, and comparing the measurement to athreshold, wherein if the measurement is within the threshold the newcomponent is determined to be within said spatial proximity. The signalstrength or time-of flight is directly related to distance, so themeasurement that is taken and compared to the threshold may be the rawmeasure of received signal strength or flight time, or could ameasurement converted to a measure of distance. As another example,multiple first components in different luminaires may take a respectivemeasurement of the received signal strength or ToF of the signal fromthe new component, and these are compared to make the determination asto which is most proximate (and therefore within the relevant proximityaccording to the predefined test). E.g. either each first componentreports its measurement to each other first lamp and each performs itsown comparison, or one of the first components takes on the role of thecomparison according to some distributed protocol, or all themeasurements could be submitted to a central controller which performsthe comparison and returns the result to the first lamps. Further, notethat the first component could instead perform the comparison, but thenew lamp takes the measurement(s) and then reports them to the firstlamp. Further, as yet another example, the measure of distance could bebased not on a signal sent between the new component and the firstcomponent(s), but instead between the new component and a plurality ofreference nodes of a positioning network such as an indoor positioningsystem, which is used to compute the positions relative to thepositioning network using a technique such as triangulation,trilateration, multilateration or fingerprinting. Given the positions ofthe first component(s) or their respective luminaire(s), the distance(s)of the new component from the first component(s) can then be determined(either centrally or at each first component), and used in a similarmanner to any of those described above.

As an alternative to the received signal strength or ToF based approach,the first component may be configured to perform said detection ofwhether the new component is within said spatial proximity (according tosaid predefined test) by: checking whether a signal is received from thenew component via a constrained signaling channel whereby propagation ofthe signal is limited by a physical property of the luminaire, whereinif the signal is received the new component is determined to be withinsaid spatial proximity.

In embodiments, said physical property of the respective luminaire maycomprise a power supply circuit powering the components of therespective subgroup, and said constrained signalling channel may be viamodulation of a voltage and/or current of the power supply circuit.

Or as another option, the constrained signalling channel may be viacoded light, ultrasound and/or radio, and said physical property of therespective luminaire may comprise at least part of a housing of theluminaire which at least partially blocks the propagation of the light,radio or ultrasound signal, the signaling channel thereby beingconstrained.

In embodiments, the first component may be configured to perform saiddetecting of the new component by receiving a message from the newcomponent via any of: a signal modulated into a voltage and/or currentof a power supply circuit powering the respective subgroup of componentsin the respective luminaire; or coded light, radio or ultrasound.

In embodiments, the first component may be configured to perform saidcheck for the previously-present component by attempting to communicatewith the previously-present component via any of: modulation of avoltage and/or current of a power supply circuit powering the respectivesubgroup of components in the respective luminaire; or coded light,radio, ultrasound, or near field communication (NFC).

According to another aspect disclosed herein, there is provided a firstlamp for use as one of a system of replaceable components comprising aplurality of components connected in a wireless network, and at leastone unconnected component available to join the network; wherein thecomponents are to be divided amongst a plurality of luminaires with eachluminaire comprising a respective subgroup of the components includingat least one lamp and with each subgroup having a respective subgroup IDidentifying the respective subgroup within the network; and wherein thefirst lamp is configured to perform operations of: detecting anunconnected one of the components available to join the network;detecting whether a previously-present one of said components from thesame respective one of said subgroups as the first component is missingfrom the network; and in response to the detection that thepreviously-present component is missing from the network, causing theunconnected component to be joined to the wireless network under acollective ID, and to be assigned to the same respective subgroup as thefirst component under the same respective subgroup ID.

According to another aspect disclosed herein, there is provided acomputer program product for operating a first component as one of asystem of replaceable components comprising a plurality of componentsconnected in a wireless network and at least one unconnected componentavailable to join the network; wherein the components are to be dividedamongst a plurality of luminaires with each luminaire comprising arespective subgroup of the components including at least one lamp andwith each subgroup having a respective subgroup ID identifying therespective subgroup within the network; and wherein the computer-programproduct comprises code embodied on a computer-readable storage mediumand/or being downloadable therefrom, and being configured so as when runon one or more processors in the first component to perform operationsof: detecting whether a previously-present one of said components fromthe same respective one of said subgroups as the first component ismissing from the network; and in response to the detection that thepreviously-present component is missing from the network, causing theunconnected component to be joined to the wireless network under acollective ID, and to be assigned to the same respective subgroup as thefirst component under the same respective subgroup ID.

According to another aspect disclosed herein, there is provided a methodperformed in a system of replaceable components comprising a pluralityof components connected in wireless a network, and at least oneunconnected component available to join the network; wherein thecomponents are divided amongst a plurality of luminaires, each luminairecomprising a respective subgroup of the components including at leastone lamp, and each subgroup having a respective subgroup ID; and whereinaccording to said method: a first one of the components automaticallydetects whether a previously-present one of said components in the samesubgroup as the first component is missing from the network; and inresponse to the detection that the previously-present component ismissing from the network, said first component automatically causes theunconnected component to be joined to the wireless network under acollective ID, and to be assigned to the same respective subgroup as thefirst component under the same respective subgroup ID.

In embodiments, the first lamp, computer program and/or method may befurther configured in accordance with any of the features mentionedabove or elsewhere herein.

According to further alternative or additional aspects of the presentdisclosure, there are provided an apparatus, method and computer programfor detecting whether lamps are in the same luminaire, and foridentifying those lamps. This may be used to detect a replacement lampas mentioned above, and/or for other purposes such as to detect lamps inthe same luminaire for the purpose of commissioning.

For instance, a project to replace all the old-fashioned tubes in anoffice with TLEDs, or the like, will require a commissioning process.Consider the process of commissioning an arrangement of wirelessluminaires in which the wireless interface is included in eachluminaire's housing on a per luminaire basis (as opposed to a wirelessinterface being included in each individual wireless lamp). To do this,the commissioning technician has to stand underneath each luminaire thathe or she intends to commission (or in visible vicinity of it), andselect what he or she believes to be that luminaire on the userinterface of a commissioning tool (e.g. a dedicated commissioning deviceor a commissioning application running on a mobile user terminal such asa smartphone, tablet or laptop). The commissioning tool then broadcastsa commissioning request comprising an identifier of the selectedluminaire, and in response the luminaire having that identifier willemit a visual indication (e.g. by blinking via its lamp(s) or a separateindicator light). This way the technician can check whether the selectedluminaire is indeed the luminaire that he or she intends to commission.If so, the technician then confirms this to the commissioning tool, andin response the tool adds the confirmed luminaire to a wireless networkfor controlling the lights in a subsequent operational phase. Thecommissioning technician then repeats this for each luminaire to becommissioned (e.g. every luminaire in the office).

Consider now the case where a wireless interface is included in eachindividual wireless lamp. In typical office applications, four TLEDs areincluded per luminaire. An instant-fit connected TLED based solutionhence results in a four times higher number of wireless nodes than thecompeting approaches applying either a wireless luminaire-renovation kit(for instance the Philps Evokit product) or a new wireless luminaire.Thus the present state-of-the-art solutions for connected TLEDs willresult in a very high commissioning effort due to the very high numberof wireless nodes per space. I.e. the commissioning technician wouldhave to perform the above-described steps for each lamp, not just eachluminaire, by standing under or in visual vicinity of each individuallamp and having it blink to confirm its identity, then individuallyjoining each lamp to the control network. The commissioning technicianmay also have to identify which lamps are part of the same luminaire inorder to allow them to be controlled (e.g. dimmed) as a group aftercommissioning phase is over. Further, such a process typically requiresa relatively highly skilled commissioning technician.

Hence according to one aspect of the present disclosure, there isprovided a first lamp for use in a luminaire, the first lamp comprising:a transmitting circuit configured to transmit, and/or a receivingcircuit configured to receive, one or more signals via a constrainedsignalling medium whereby propagation of the signals is constrained by aphysical characteristic of the luminaire; and a controller configured todetect, based on the transmission and/or reception of said one or moresignals via said constrained signalling medium, that one or more other,second lamps are present in the same luminaire as the first lamp, and toidentify the one or more second lamps based on the transmission and/orreception of said one or more signals.

That is, the fixture has a containing or confining effect on the signal,acting as a physical barrier or hindrance, and based on this thecontroller on the first lamp can be configured to infer the presence ofthe one or more second lamps in the same luminaire, and to identifythose lamps.

In a particularly preferred embodiment, this is achieved by signallingthrough a power supply circuit (e.g. ballast) incorporated within theluminaire, i.e. so said signalling medium is the power supply circuit ofthe luminaire, and said physical characteristic constraining the signalis the fact that the signal only travels through the local power supplycircuit (e.g. ballast) within the luminaire and so is only conveyed toother lamps sharing the same power supply circuit.

Alternatively however, the constrained signalling medium may comprisecoded light, ultrasound and/or radio, with the propagation of said oneor more signals being constrained by at least part of a housing of theluminaire.

In embodiments, the first lamp may comprise at least the transmittingcircuit, configured to transmit at least a respective one of saidsignals to each of the one or more second lamps, and the controller maybe configured to detect the one more second lamps based on receivingback a response message from each of the second lamps in response to thetransmission of the respective signal. Preferably, the first lampcomprises an alternative interface (e.g. a wireless interface) forreceiving messages via another (e.g. wireless) medium other than saidconstrained signalling medium, and the controller is configured to usesaid alternative interface to receive said response message via saidother medium. This other medium may be one that is not subject to saidphysical constraint imposed by the luminaire (either not constrained atall, or at least to a lesser extent). E.g. the wireless interface may bea ZigBee, Wi-Fi or Bluetooth interface.

In embodiments wherein the constrained signalling medium comprises thepower supply circuit within said same luminaire for supplying power tothe first and second lamps, the transmitter is configured to performsaid transmission by modulating the power supplied by said power supplycircuit, the propagation of the one or more signals thereby beingconstrained to the power supply circuit within the same luminaire as thefirst and second lamps.

The transmitting circuit may be configured to perform said modulation bymodulating a load placed on the power supply circuit by the first lamp.E.g. this modulation may comprise on-off keying, whereby the load isselectively shorted, or selective switched in and out of the powersupply circuit.

In alternative or additional embodiments, the first lamp may comprise atleast the receiving circuit, configured to receive at least a respectiveone of said signals from each of the one or more second lamps via saidconstrained signalling medium, and the controller may be configured toidentify the one or more second lamps based on a message conveyed ineach of the respective received signals.

In embodiments where the constrained signalling medium comprises thepower supply circuit within said same luminaire for supplying power tothe first and second lamps, the propagation of the one or more signalsis thereby constrained to the power supply circuit within the sameluminaire as the first and second lamps; and the receiving circuit isconfigured to receive said signal by detecting modulations in the powersupplied by said power supply circuit of the luminaire.

In embodiments, the first lamp may be configured to use a combination oftwo or more methods to detect which lamps are in the same luminaire.That is, the transmitting circuit may be configured to transmit, and/orthe receiving circuit may be configured to receive, a respective one ormore signals via each of a plurality of different a signalling media,each being a medium whereby propagation of the signals is constrained bya physical characteristic of the luminaire; and the controller may beconfigured to is configured detect and identify the one or more other,second lamps in the same luminaire as the first lamp based on thetransmission and/or reception of the one or more signals communicatedvia each of said plurality of signalling media.

In embodiments, the power supply used for the signalling is a ballast.In embodiments, the first lamp may take the form of a retrofittable LEDreplacement for a florescent tube, said ballast being a ballast forpowering a fluorescent tube.

In embodiments, the first lamp may comprise a wireless interface (e.g.ZigBee, Wi-Fi or Bluetooth) for receiving a respective beacon from eachof a plurality of other lamps via another, wireless medium other thansaid constrained signalling medium, said plurality of other lampsincluding but not being limited to said one or more second lamps; andthe controller may be configured to use the wireless interface tomeasure a received signal strength of the respective beacon from each ofsaid plurality of other lamps, to determine a subset of lamps fromamongst the plurality of lamps based on the received signal strengths,and then to use the one or more signals transmitted and/or received viasaid constrained signalling medium to detect and identify the one ormore second lamps from amongst said subset. For example, the subset maybe selected as those whose beacons are received with above a thresholdsignal strength, or may be selected as the N lamps whose beacons arereceived with the strongest signal strengths (where N is a predeterminedinteger).

In embodiments, the constrained signalling channel can also be used todetect a replacement for a replaced lamp. That is, in embodiments: eachof the first and second lamps may be configured to communicate via awireless network; at least one of the second lamps may comprise areplacement component being a replacement of a previous instance of thatlamp previously used in the luminaire; and the controller of the firstlamp may be further configured to automatically detect the replacementlamp as being a replacement based on the transmission and/or receptionof at least one of the signals via said constrained signalling channel,and to automatically cause the replacement lamp to be joined to saidwireless network upon the replacement.

Alternatively or additionally, the controller of the first lamp mayconfigured to automatically detect within the luminaire, based on thetransmission and/or reception of at least one further signal via saidconstrained signalling channel, a replacement lamp being a futurereplacement for one of the one or more second lamps, and in response toautomatically cause the replacement lamp to be joined to said wirelessnetwork.

According to another aspect disclosed herein, there is provided aluminaire comprising a first lamp and one or more second lamps, whereinthe first lamp comprises: a transmitting circuit configured to transmit,and/or a receiving circuit configured to receive, one or more signalsvia a constrained signalling medium whereby propagation of the signalsis constrained by a physical characteristic of the luminaire; and acontroller configured to detect, based on the transmission and/orreception of said one or more signals via said constrained signallingmedium, that one or more other, second lamps are present in the sameluminaire as the first lamp, and to identify the one or more secondlamps based on the transmission and/or reception of said one or moresignals.

According to another aspect disclosed herein, there is provided acomputer program product for operating a first lamp within a luminaire,the computer program product comprising code embodied on acomputer-readable storage medium and/or being downloadable therefrom,and being configured so as when run on the first lamp to performoperations of: transmitting from the first lamp, and/or a receiving atthe first lamp, one or more signals via a constrained signalling mediumwhereby propagation of the signals is constrained by a physicalcharacteristic of the luminaire; and based on the transmission and/orreception of said one or more signals via said constrained signallingmedium, that one or more other, second lamps are present in the sameluminaire as the first lamp, and identifying the one or more secondlamps based on the transmission and/or reception of said one or moresignals.

According to another aspect disclosed herein, there is provided a methodof commissioning a luminaire comprising a first lamp and one or moresecond lamps, the method comprising: transmitting from the first lamp,and/or a receiving at the first lamp, one or more signals via aconstrained signalling medium whereby propagation of the signals isconstrained by a physical characteristic of the luminaire; and based onthe transmission and/or reception of said one or more signals via saidconstrained signalling medium, that the one or more second lamps arepresent in the same luminaire as the first lamp, and identifying the oneor more second lamps based on the transmission and/or reception of saidone or more signals.

According to another aspect disclosed herein, there is provided a secondlamp for use in a luminaire, the second lamp comprising: a receivingcircuit configured to receive a signal from a first lamp via aconstrained signalling medium whereby propagation of the signals isconstrained by a physical characteristic of the luminaire; and acontroller configured to detect the reception of said signal andidentify the first lamp based on said signal. In embodiments the secondlamp further comprises an alternative interface (e.g. a wirelessinterface such as a ZigBee interface) for transmitting messages viaanother (e.g. wireless) medium other than said constrained signallingmedium; wherein the controller may be configured to use said alternativeinterface to respond to said signal received over said constrainedsignalling medium, by sending a message identifying the second lamp tothe first lamp via said other medium.

In embodiments, any of the first lamp, second lamp, system, method andcomputer program may further comprise features in accordance with any ofthe teachings herein.

According to further aspects disclosed herein, to reduce the burden ofcommissioning, it would therefore be desirable to provide acommissioning process that does not require commissioning of each lampindividually. For example this could be used to automatically pre-groupall the TLEDs or other such retrofittable lamps installed within a givenluminaire, upfront at the start of commissioning, so as to allow them tobe commissioned as a group and preferably also to allow then to besubsequently controlled via a single wireless address in the operationalphase.

The following provides an auto-grouping and commissioning approach for aTLED-based wireless system or other such system ofwireless-communication enabled lamps (e.g. downlights in a conferenceroom or spotlights in a hotel lobby), which can allow a user such ascommissioning agent or value-added-reseller (VAR) to more easilyorganize the entire end-to-end migration to wireless lighting control(e.g. to wirelessly controlled LED-based lamps). The installation mayeven be performed by a low cost employee, because in embodiments, fromthe user's perspective it need only involve simple re-lamping. Forinstance the commissioning process disclosed herein may be used for a“stock and flow” business (wherein “stock-and-flow” involves bothselling via the wholesale channel and using a “moderately trained”re-lamping labour workforce rather than electricians and highly trainedcommissioning experts).

As well as new TLEDs installation projects, or such like, in embodimentsthe process disclosed herein also allows for “out-of-the box” fieldreplacement of broken TLEDs (or other such lamps), enablingauto-grouping without involvement of a remote control or a commissioningexpert.

Furthermore, as well as installing or replacing TLEDs or other wirelesslamps in the same luminaire, in embodiments the commissioning processdisclosed herein may also be applied to other situations where it isappropriate to treat a cluster of lamps as a group. As an example,consider a room such as a kitchen with discrete clusters of spot lightsor other such task lights: e.g., a cluster of under-cabinet spots, acluster of spots over a work-surface island, etc. Another example is abig chandelier with many candle-style light bulbs. As another example,the lamps in different zones of a room such as an office may be treatedas a group, e.g. one group per cubicle.

According to one aspect disclosed herein, there is provided a first lampfor use as one of a plurality of wireless-communication enabled lamps,each respective one of the lamps being operable in a first mode in whichthe respective lamp appears to a commissioning tool as awaitingcommissioning and a second mode in which the respective lamp does notappear to the commissioning tool as awaiting commissioning, with each ofthe lamps being configured to begin in the first mode as part of acommissioning process (i.e. each lamp is configured to participate in acommissioning process, and at the beginning of its participation in thecommissioning process, each lamp starts out in the first mode). Forinstance, the first mode may be the Factory New (FN) mode of the ZigBeeLight Link protocol or other such ZigBee protocol, and the second modemay be the non-FN mode of the ZigBee Light Link protocol or other ZigBeeprotocol.

The first lamp is configured to perform the following steps. To begin,the first lamp triggers a second one or more of the lamps to switch tothe second mode (e.g. non-FN mode), so that during the commissioningprocess the one or more second lamps will not to appear to thecommissioning tool as awaiting commissioning. Preferably, the first lampis configured to select the one or more second lamps to be treated inthis manner on the basis of being within a same spatially-defined groupas the first lamp, e.g. a same spatial cluster. That is, the one or moresecond lamps are selected on the basis of having a certain predeterminedspatial relationship with the first lamp, e.g. according to somepredefined test of proximity, such as being within a same predefinedspatial region defined relative to the first lamp. In a particularlyadvantageous application, the first lamp is configured to perform saidtriggering of the one or more second lamps to switch to the second modeon the basis of them being in a same luminaire as the first lamp. I.e.the one or more second lamps are those detected by the first lamp asbeing in the same luminaire as the first lamp (see below).

Following said triggering of the one or more second lamps to switch tothe second mode, the first lamp operates itself in the first mode (e.g.FN mode) so that the first lamp will appear to the commissioning tool asawaiting commissioning, thereby representing the first and second lampsjointly to the commissioning tool. The first lamp then interacts withthe commissioning tool on behalf of said one or more second lamps, inorder to commission the first and second lamps as a group (there arevarious options for this interaction by the first lamp, whether by justinitially contacting the tool to initiate the commissioning between thetool and second lamps, or by playing a greater role in coordinating thecommissioning of the second lamps).

Thus by artificially manipulating the Factory New mode (or such like),it is possible to provide an automatic “pre-commissioning” whereby thelamps are automatically treated as a group for the purpose ofcommissioning, with one lamp (the first lamp) acting as therepresentative of the others. Advantageously, the one or more secondluminaries in the same group (e.g. same luminaire) are thus hidden fromthe commissioning tool, and from the perspective of the user performingthe commissioning, the process can proceed on a per group (e.g. perluminaire) basis.

In embodiments, each respective lamp is configured to switch to thesecond mode (e.g. non-FN mode) in response to joining a wireless networkof a predetermined wireless networking protocol (e.g. the ZigBee LightLink protocol). In this case, the first lamp may be configured toperform said switching of the one or more second lamps to the secondmode (e.g. non-FN mode) by emitting a first message causing the secondlamps to join a first wireless network created by the first lampaccording to said wireless networking protocol, thereby causing thefirst and second lamps switch to the second mode (e.g. non-FN mode); andsaid step of the first lamp operating in the first mode (e.g. FN mode)may comprise the first lamp exiting the first wireless network,following said switching of the first and second lamps to the secondmode (e.g. non-FN mode), so as to return itself to the first mode (e.g.FN mode) and thereby be discoverable to the commissioning tool.

In embodiments, the first lamp may be configured to detect a secondmessage (e.g. ZigBee beacon) emitted by each of one or more of saidplurality of lamps, each second message communicating an attribute ofthe respective lamp (e.g. an identifier such as its address); and thefirst lamp may be further configured to determine whether to become amaster for purpose of the commissioning process by comparing acorresponding attribute of the first lamp with the attribute received ineach of one or more of the detected second signals, and to perform theabove pre-commissioning steps on condition of being the master. I.e. thefirst lamp, which acts as a representative of the one or more secondlamps in its same group, also acts as a master and treats the one ormore second lamps in its same group (e.g. same luminaire) as slaves forthe purpose of the commissioning, such that it will instruct itsrespective second lamps to perform one or more actions as part of thecommissioning process. The first lamp elects itself as master based on adistributed protocol whereby each lamp compares a value assigned toitself with the value of the same attribute assigned to other lamps asreceived in their beacons. E.g. the master may be the lamp with lowestaddress from amongst those detected.

In embodiments, the first lamp is configured so as, subsequent to thecommissioning of said first and second lamps, to allow a next one ofsaid plurality of lamps in a further luminaire or group to become amaster in order to commission the lamps of a further luminaire or group.The first lamp does this by indicating in a message from the first lampthat (despite the fact that it is back in the first mode and beaconing)the first lamp has already been a master. Thus it will not be taken intoaccount again by the distributed protocol for selecting the next master.

The commissioning that is performed on a group basis may comprise one ormore of a number of possible commissioning operations.

For example, the first lamp may be configured to receive identifiers ofthe one or more second lamps, e.g. via the first wireless network (e.g.the local ZigBee network created between the first and second lamps), orvia other means such as coded light or load modulation (see later). Saidinteraction with the commissioning tool may then comprise the first lampreporting the identifiers of the one or more second lamps to thecommissioning tool. Alternatively, said interaction may comprisereceiving, on behalf of the first and second lamps, a request from thecommissioning tool; and the first lamp may be configured, in response,to send a message to the one or more second lamps via the first wirelessnetwork, causing the one or more second lamps to report their ownrespective identifiers to the commissioning tool.

As another example, said interaction may comprise receiving, on behalfof the first and second lamps, a request from the commissioning tool;and the first lamp may be configured, in response, to cause one or moreof the first and second lamps to produce a visual indication to the userof the commissioning tool, indicating a grouping of the first and secondlamps collectively (e.g. only the first lamp blinks, or the first lampcauses the first and second lamps to blink together). This enables auser to confirm that the luminaire or group of lamps being commissionedis indeed the luminaire or group the user intended, and to confirm aphysical location of the group of lamps being commissioned.

As another example, said interaction with the commissioning tool maycomprise: the first lamp joining a second wireless network, and alsocausing the one or more second lamps to exit the first wireless networkin order to join the second wireless network, the second network beingfor controlling the lamps once the commissioning process is finished.The second network may use the same wireless networking protocol as thefirst network, e.g. it may be a further ZigBee network. This secondnetwork may be a wider network incorporating the lamps of multipleluminaires or groups. It is used later in the operational phase to allowthe lamps to be controlled (e.g. dimmed based on commands from alighting controller and/or sensor readings from one or more wirelesssensors).

In further embodiments, said interaction with the commissioning tool maycomprise: being assigned, by the commissioning tool, a group address forjointly controlling said the first lamp and the one or more second lampsvia the second wireless network.

In yet further embodiments, the first lamp may be further configured toperform steps of: after the commissioning process, detecting areplacement for one of the one or more second lamps in the sameluminaire or group (the replacement lamp beginning in the first modeupon replacing said one of the second lamps), and causing thereplacement lamp to join the second wireless network (and thereby alsocausing the replacement lamp to switch to the second mode, e.g. non FNmode). Preferably the first lamp is also configured to cause thereplacement lamp to be added to the group address. Thus the replacementlamp gets allocated to the same group(s) that the lamp used to belongto, and fully takes over the role of the broken lamp.

Note that in any given embodiment, any one or more of the groupcommissioning operations mentioned above (involving the interaction withthe commissioning tool) may be applied alone or in combination. Further,in embodiments, any of these may be performed in response to a requestfrom the commissioning tool, and where multiple such commissioningoperations are involved, any of them may be performed in response to thesame request message from the commissioning tool or separate requestsfrom the tool.

According to another aspect disclosed herein, there is provided aluminaire comprising a first lamp and one or more second lamps, eachrespective one of the lamps being operable in a first mode in which therespective lamp appears to a commissioning tool as awaitingcommissioning and a second mode in which the respective lamp does notappear to the commissioning tool as awaiting commissioning, with each ofthe lamps being configured to begin a commissioning process in the firstmode; wherein the first lamp is configured to perform steps of:triggering a second one or more of the lamps to switch to the secondmode, so that during the commissioning process the one or more secondlamps will not to appear to the commissioning tool as awaitingcommissioning; following said switching of the one or more second lampsto the second mode, operating in the first mode so that the first lampwill appear to the commissioning tool as awaiting commissioning; andinteracting with the commissioning tool on behalf of said one or moresecond lamps, in order to commission the first and second lamps as agroup.

According to another aspect disclosed herein, there is provided a systemcomprising a plurality of wireless-communication enabled lamps includinga first lamp and one or more second lamps, each respective one of thelamps being operable in a first mode in which the respective lampappears to a commissioning tool as awaiting commissioning and a secondmode in which the respective lamp does not appear to the commissioningtool as awaiting commissioning, and each of the lamps being configuredto begin a commissioning process in the first mode; wherein the firstlamp is configured to perform steps of: triggering a second one or moreof the lamps to switch to the second mode, so that during thecommissioning process the one or more second lamps will not to appear tothe commissioning tool as awaiting commissioning; following saidswitching of the one or more second lamps to the second mode, operatingin the first mode so that the first lamp will appear to thecommissioning tool as awaiting commissioning; and interacting with thecommissioning tool in order for the first and second lamps to becommissioned as a group.

According to another aspect disclosed herein, there is provided a methodof operating a plurality of wireless-communication enabled lamps, eachrespective one of the lamps being operable in a first mode in which therespective lamp appears to a commissioning tool as awaitingcommissioning and a second mode in which the respective lamp does notappear to the commissioning tool as awaiting commissioning; the methodcomprising steps of: beginning a commissioning process with each of thelamps in the first mode; causing a second one or more of the lamps toswitch to the second mode, so that during the commissioning process theone or more second lamps will not to appear to the commissioning tool asawaiting commissioning; following said switching of the one or moresecond lamps to the second mode, operating the first lamp in the firstmode so that the first lamp will appear to the commissioning tool asawaiting commissioning; and using the first lamp to interact with thecommissioning tool in order for the first and second lamps to becommissioned as a group.

According to another aspect disclosed herein, there is provided acomputer program product for operating a first lamp as one of aplurality of wireless-communication enabled lamps, each respective oneof the lamps being operable in a first mode in which the respective lampappears to a commissioning tool as awaiting commissioning and a secondmode in which the respective lamp does not appear to the commissioningtool as awaiting commissioning, and each of the lamps being configuredto participate in a commissioning process starting in the first mode;wherein the computer program product comprises code embodied on acomputer-readable storage medium and/or being downloadable therefrom,and being configured so as when run on the first lamp to perform stepsof: triggering a second one or more of the lamps to switch to the secondmode, so that during the commissioning process the one or more secondlamps will not to appear to the commissioning tool as awaitingcommissioning; following said switching of the one or more second lampsto the second mode, operating the first lamp in the first mode so thatthe first lamp will appear to the commissioning tool as awaitingcommissioning; and interacting with the commissioning tool in order forthe first and second lamps to be commissioned as a group.

In embodiments, any of the first lamp, luminaire, system, method andcomputer program may further comprise features in accordance with any ofthe teachings herein.

Further, note that the scope of the present disclosure can also extendto the commissioning of other components, not just lamps, and/or todetecting whether one or more other components are in the same luminaireas a lamp. Hence in any of the above embodiments of any of the aboveaspects described in relation to lamps, or anywhere herein where thereis mentioned a lamp, the lamp may be more read generally as a component.In embodiments of any aspect, the first lamp is indeed a lamp, but wherethere are recited a one or more second lamps, these may be read moregenerally as one or more second components. For example, the one or moresecond components may comprise one or more components that may be foundhoused in a luminaire along with the first lamp, e.g. a smoke detectorcomponent, a security camera, a driver for driving the lamp, and/or abattery such as an emergency battery for powering the first lamp.

In embodiments, this latter aspect may be used in conjunction with anyof features of any of the other aspects or embodiments disclosed aboveor elsewhere herein, or may be used independently of these.Particularly, note that this aspect relating the replacement ofcomponents may be used together with any of the initial commissioningfeatures disclosed herein, or with a different commissioning process;and/or the detection of the replacement lamp may be implemented with themechanism disclosed herein for detecting whether lamps or components arein the same luminaire, or a different detection mechanism (e.g. alook-up based on pre-stored mapping of lamps to luminaires).

According to another aspect, there is a provided a first lamp configuredto perform the above method. According to another aspect, there isprovided a luminaire comprising this first lamp and the one or moreother components.

BRIEF DESCRIPTION OF THE DRAWINGS

To assist understanding of the present disclosure and to show howembodiments may be put into effect, reference is made by way of exampleto the accompanying drawing in which:

FIG. 1 is a schematic illustration of an environment in which a lightingsystem is deployed,

FIG. 2 is a schematic block diagram of a luminaire comprising aplurality of lamps,

FIG. 3 is a schematic block diagram of a lamp,

FIG. 4 is a schematic wiring diagram for a luminaire comprising aplurality of lamps,

FIG. 5 is a schematic circuit diagram of a ballast,

FIG. 6 is a schematic circuit diagram of another ballast,

FIG. 7 is a schematic circuit diagram of a lamp,

FIG. 8 is a schematic timing diagram showing a current sensed by a lamp,and

FIG. 9 is a schematic state diagram of a lamp.

DETAILED DESCRIPTION OF EMBODIMENTS

The following provides an auto-commissioning method for auto-grouping ofmultiple connected TLED tubes, or other such wireless lamps, which areresiding within the same luminaire. In embodiments, the auto-groupingmethod builds upon the insight that TLEDs residing within the luminaireare wired to one shared fluorescent ballast. To exploit this, averification that TLEDs share the same ballast is performed viaintentional load change patterns imprinted by one master TLED onto theballast. The load change experienced by the fluorescentballast—depending on the ballast type—results either in shifts of theballast frequency and/or the lamp currents provided by the fluorescentballast towards the other, slave TLEDs within the luminaire. Upondetection of the frequency or current shift patterns caused by themaster TLED, each of the one or more slave TLEDs can conclude withcertainty that it shares the same the same ballast and hence that it iswithin the luminaire with the master TLED.

The following disclosure also provides a network joining mechanismoptimized for TLEDs. Initially only the Master Connected TLED is visibleas Factory New lamp to the installer. Once the installer adds the MasterTLED to the ZigBee network, which is set up by a lighting bridge orremote control, the slave TLEDs residing within the same luminaire arethen enabled to join the same ZigBee network as well without anyadditional action being required from the installer. The disclosurefurther provides a “ballast-load-drop-based” auto-grouping method aimedat the replacement of broken connected TLEDs without requiring installerintervention.

In the following description, first will be described anauto-commissioning process for use in an initial commissioning stage,e.g. the first time a room or building is installed with a system ofTLEDs. Later will be described a re-lamping process for replacing one ormore individual wireless lamps at a later stage (after the lamps havebeen commissioned and already put into day-to-day use). E.g. there-lamping may be to replace one or more broken TLEDs.

To increase the speed of the TLED auto-grouping, preferably the initialcommissioning procedure starts with a faster and less intrusive (butalso less deterministic) evaluation method. That is, firstly the TLEDswithin the same luminaire can be assumed to be likely to be within arelatively small “wireless” vicinity compared to the typical spacing tothe nearest neighbour luminaire. Hence based upon radio RSSI (oralternatively coded light), the TLEDs may be grouped into buckets suchas “likely within same luminaire”, “maybe in same luminaire”, “unlikelywithin same luminaire”. Then, starting from the initial RSSI-based TLEDbuckets, the method proceeds to use the load modulation to determinewith certainty which of the TLEDs are connected to a shared fluorescentballast, and are therefore for sure located within the same luminaire.

The presented auto-commissioning approaches are particularly suitablefor automatically grouping connected TLEDs located within one luminaire.Nonetheless, whilst embodiments may be described in terms of TLEDs byway of illustration, note that the techniques disclosed herein can alsoapply to the grouping of other types of wireless lamp, e.g. other typesof LED-based lamp such as retrofittable LED-based replacements fortraditional filament bulbs, or even non-LED based lamps.

Some example embodiments are now described in more detail in relation toFIGS. 1 to 8.

FIG. 1 illustrates an example lighting system in which the disclosedtechniques may be implemented. The system comprises one or moreluminaires 4 installed or otherwise deployed in an environment 2,arranged to emit illumination in into that environment 2. Theenvironment 2 may be an indoor space such as one or more rooms and/orcorridors of a building; or an outdoor space such as a park, garden,road, or outdoor parking area; or a partially covered space such as astadium, structured parking facility or gazebo; or any other space suchas an interior of a ship, train or other vehicle; or any combination ofsuch possibilities.

Each of the luminaires 4 comprises at least one respective lamp such asan LED-based lamp, gas-discharge lamp or filament bulb, plus anyassociated support, casing or other such housing. Each of the luminaires4 may take any suitable form such as a ceiling or wall mountedluminaire, a free standing luminaire, a wall washer, a chandelier; or aless conventional form such as embedded lighting built into an item offurniture, a building material such as glass or concrete, or any othersurface. In general a luminaire 4 may be any type of illumination devicefor emitting illumination into the environment 2. In embodiments theluminaire 4 is one which is designed to emit illumination suitable forilluminating an environment 2, i.e. functional lighting—a devicedesigned and used to allow users to see and find their way about withinthe environment 2, providing or substantially contributing to theillumination on a scale adequate for that purpose. Nonetheless, insteadof providing functional lighting (or as well as providing functionallighting), it is also possible that the luminaire 4 is a device designedto generate a lighting effect, such as task lighting, accent lighting ormood lighting; e.g. an embedded luminaire embedded in a surface whichchanges colour.

An example of one of the luminaires 4 is shown in FIG. 2. Each luminaire4 comprises a power supply circuit 10, one or more lamps 12, and ahousing 14. In fact, at least one of the luminaires 4, and inembodiments some or all of the luminaires 4, each comprise a pluralitylamps 12. In this case, the luminaire 4 comprises an internal powersupply circuit 10 of the luminaire, and sockets for connecting aplurality of lamps 12 to the power supply circuit 10 in order to powerthose lamps 12. E.g. by way of example, FIG. 2 shows four lamps 12 a, 12b, 12 c, 12 d in the same luminaire 4 (but note that while the followingembodiments may be descried in terms of this example, this is notlimiting and the luminaire 4 may support other numbers of lamps 12).Being in the same luminaire 4 herein means the lamps in question sharethe same power supply circuit 10 and the same housing 14. Hence thelamps 12 a-d may be described as “cohabiting” in the same luminaire 4.In general the “housing” 14 may refer to any casing and/or supportingstructure of the fixture. E.g. in embodiments the housing 14 maycomprise an opaque upper and/or side-wall casing for mounting on theceiling, plus a plurality of sockets mechanically connected to the uppercasing, and a lower diffuser element for diffusing the illuminationemitted downwards by the lamps 12 a-d into the environment 2. In anotherexample form however, the “housing” 14 may take the form of a hangingstructure such as a chandelier style structure supporting a plurality ofsockets (and the casing element is not necessarily present).

The power supply circuit 10 connects to an upstream power supply 16,e.g. the mains supply, and is configured to generate a power supplysuitable for powering lamps based on this. E.g. typically the powersupply circuit 10 takes the form of a ballast, i.e. a device forlimiting the current supplied to the lamps in its luminaire 4.

In embodiments, one or more of the luminaries 4 may each take the formof a fluorescent luminaire having sockets for accepting a plurality offluorescent tubes. In this case, the lamps 12 a-d may take the form of“tube LEDs” (TLEDs), i.e. retrofittable LED-based lamps designed toreplace the fluorescent tubes in a conventional fluorescent luminairedesigned for traditional fluorescent tubes. For instance, most officeluminaires take two to four TLED tubes per fixture (though it is notexcluded that some, but not all, others of the luminaires may have onlya single TLED).

Table 1 shows an overview of the typical number of TLED tubes 12 andballasts 10 per luminaire 4 for the EMEA (Europe, Middle East andAfrica) and NAM (North American) regions. In almost all situations, onlyone ballast 10 is present per luminaire 4. In the USA, TLEDs 12 a-dwithin the same fixture are always connected to single fluorescentballast 10.

Number of Number of Region Luminaire type TLED tubes ballasts EMEA 2 ft× 2 ft square luminaire 4 1 5 ft 1-lamp luminaire 1 1 5 ft 2-lampluminaire 2 1 (or in some rare cases 2) 4 ft 1-lamp luminaire 1 1 4 ft2-lamp luminaire 2 1 NAM 2 ft × 2 ft troffer 4 1 2 ft × 4 ft troffer 4or 3 1

FIG. 3 illustrates an individual TLED lamp 12, which may represent anyof the lamps 12 a-d used in the luminaire 4 described in relation toFIG. 2.

As shown, the lamp 12 comprises an actual lighting element 18, such as astring or other array of LEDs. The lamp 12 also comprises at least oneend-cap 20, and in the case of a TLED replacing a fluorescent tube, thelamp 12 in fact comprises two end-caps 20 i, 20 ii. Each end-cap 20 i,20 ii comprises a respective connector 22 for connecting the lamp 12 tothe ballast 10 via a socket of the luminaire 4, and thereby connectingthe lighting element 18 to the power supplied by the ballast 10. In thecase of a fluorescent tube, each connector 22 in fact comprises twoterminals (a pair of pins) being either terminal of a receptivefilament, though in the case of a TLED replacing a fluorescent tube, thetwo terminals of each connector are typically shorted together as theneed for two terminals is a specific requirement of fluorescent tubesand is not necessarily relevant to LED-based lamps (see discussion laterin relation to FIG. 4).

Moreover, at least one end-cap 20 i of the lamp 12 is used to houseadditional components, being components specific to the fact that thelamp 12 is a wirelessly controlled and/or LED-based replacement for amore traditional lamp such as a fluorescent tube or filament bulb. Theseadditional components comprise a rectifier 23 and LED driver 24 forconverting the power supplied by the ballast 10 (designed for powering aconventional lamp such as a fluorescent tube) into power suitable fordriving an LED-based lighting element 18. The rectifier 23 is connectedto the connector(s) 22 i, 22 ii of the lamp 12, for receiving the ACpower supplied by the ballast 10 and converting it to DC. The LED driver24 is connected to the rectifier 23 and arranged to further convert thisinto an approximately constant (but in embodiments adjustable) currentsupply for powering the LED-based lighting element 18 (e.g. LED string),and thereby cause a desired light output to be emitted from the lightingelement 18. N.B. if the power supplied by the luminaire's power supplycircuit 10 is already DC, the rectifier 23 is not needed, but typicallyin the scenario of a retrofittable LED-based lamp, the power from theluminaire's own power supply circuit (e.g. ballast) 10 will indeed be ACand therefore need rectifying.

Further, the additional components in the end-cap 20 i comprise acontroller 26, and a wireless interface 28 in the form of a radiotransceiver, such as a ZigBee, Wi-Fi, 802.15.4 or Bluetooth transceiver.The controller 26 may be implemented in software stored in an embeddedmemory of the lamp 12 and run on an embedded processing device 46 of thelamp 12, or the controller 26 may be implemented in dedicated hardwarecircuitry, or configurable or reconfigurable hardware circuitry such asa PGA or FPGA. In embodiments the controller is implemented in acombination of software and dedicated hardware M1 (see FIG. 7, to bediscussed in more detail later).

In embodiments, to aid installation for best communication between lamps12 within a luminaire 4, the end-cap 20 i housing the additionalcomponents may be marked with a physical (e.g. visible) mark or marks.For instance, a physical mark may be provided at the end where the radiois, and the installer may be instructed to group the marks within aluminaire. Alternatively colour coding could be used, with a mark of onecolour at one end 20 i and a mark of another colour at the other end 20ii. E.g. a red dot on one cap (and optionally a blue dot on the othercap), and instructions may be provided that caps of the same colour gotogether.

The controller 26 is connected to the wireless interface 28 and the LEDdriver 24. The controller 26 is configured (e.g. programmed) to use thewireless interface 28 to receive lighting control commands from a manualor automated lighting controller (not shown), such as a dedicated remotecontrol device, a wireless wall switch or wall panel, or a lightingcontrol application running on a user terminal like a smartphone,tablet, laptop computer or desktop computer. In response, the controller26 then controls the driver 24 in order to control the light output ofthe lighting element 18 in accordance with the received control command.For example this may comprise turning the light on or off, dimming thelight output up or down, changing the colour of the light output, orcreating a dynamic (time-varying) lighting effect. E.g. the controller26 can adjust the current level supplied to the LEDs in the lightingelement 18 in order to dim the light output, and/or can adjust thecurrent level supplied to differently coloured ones or subarrays of theLEDs in the lighting element 18 in order to adjust the overall colour ofthe light output.

Alternatively or additionally, in a distributed system, each of theluminaires 4 may comprise one or more sensors such as an ambient lightsensor and/or occupancy sensor (not shown), and/or one or more wirelesssensors may be placed elsewhere in the environment 2. In this case thecontroller 26 may be configured to use the wireless interface 28 toreceive sensor readings from one or more of the sensors, e.g. in thesame luminaire 4 and/or a neighbouring luminaire 4. In response, thecontroller 26 can then control the light output of the lighting element18 in accordance with the sensor reading(s), e.g. to dim down or turnoff the lights when a sensor on detects that the ambient light level isbeyond a threshold or that no occupant is present within a predeterminedvicinity, or to dim up or turn on the lights when a sensor detects thatthe ambient light level is below a threshold or that an occupant ispresent in the vicinity (or more generally the control may be based on amore complex distributed control algorithm that computes an adjustmentbased on the sensor readings from multiple sensors).

In further embodiments, the controller 26 may also be configured to usethe wireless interface 28 to send status reports to the lightingcontroller (not shown), e.g. to report burning hours to date, to reportan operating temperature of the lamp, and/or to report a fault.

However, to be able to perform the various activities discussed above,or such like, this first requires the lamps 12 to be commissioned. Thatis, the lamps 12 need to be identified and joined to a wireless networksuch as a ZigBee, Wi-Fi, 802.15.4 or Bluetooth network. This wirelessnetwork then provides the means by which the wireless interface 28 oneach lamp 12 can subsequently, in the operational phase, receivelighting control commands from the lighting controller (not shown),receive sensor readings from the sensor(s), and/or send status reportsto the lighting controller. The following will be described in terms ofZigBee, but it will be appreciated that this is not necessarilylimiting.

In accordance with embodiments disclosed herein, the controller 26 isconfigured to participate in a commissioning process prior to theoperational phase. The commissioning involves one or more of the lamps12 interacting with a commissioning tool 6 used by a user 8 who isperforming the commissioning. The commissioning tool 6 may take anysuitable form, such as a dedicated remote unit, or a commissioningapplication running on a user terminal such as a smartphone, tablet orlaptop computer. Note that the commissioning tool is typically not thesame device as the lighting controller (not shown) which subsequentlycontrols the lamps 12 in the operational phase, though that possibilityis not excluded either.

The user 8 uses the commissioning tool 6 to at least instigate thecommissioning of each of the luminaires 4 he or she wishes to pull intothe control network, though in accordance with embodiments herein someor all of the rest of the process may then proceed in an automatedfashion between the lamps 12 and the commissioning tool 6.

The controller 26 on each lamp 12 is configured to be able to operateits respective lamp 12 in either a factory new (FN) mode or a nonfactory new (non-FN) mode, and to switch between these modes. Forexample these may be the FN and non-FN modes of the ZigBee Light Linkprotocol. In the FN mode, the lamp 12 appears to the commissioning tool6 as awaiting commissioning. For instance, this may be achieved by thecontroller 26 using its respective wireless interface 28 to repeatedly(e.g. periodically) emit beacons advertising that the respective lamp 12is awaiting commissioning. Alternatively, this may be achieved by thecontroller 26 setting itself to respond to queries broadcast from thetool 6 to respond that the lamp 12 is awaiting commissioning. In thenon-FN mode, the lamp 12 does not. For example, the controller 26 doesnot emit any beacons, or at least does not emit beacons advertising thelamp 12 as awaiting commissioning (e.g. it could stop emitting certainbeacons, or change the content of its beacons so as not to state thatthe respective lamp is awaiting commissioning). Alternatively, thecontroller 26 may set itself to a mode in which it does not respond tothe queries broadcast from the tool 6, or responds with a response thatthe lamp 12 is awaiting commissioning.

Thus when a lamp 12 is in the FN mode, the commissioning tool 6 willdetect the lamp 12 as awaiting commissioning and display it as such tothe user 8 through a user interface of the commissioning tool 6. In thenon-FN mode on the other hand, the commissioning tool 6 will not see thelamp 12 as awaiting commissioning and hence will not display it as suchto the user 8 through the user interface of the commissioning tool 6.

In embodiments, awaiting commissioning means at least awaiting beingjoined to a wireless network (e.g. ZigBee network) for the purposes ofsubsequent control in the operational phase. Hence in embodiments thecontroller 26 on each lamp 12 is configured to emit the above-describedbeacons when in the FN mode, but to stop emitting said beacons when inthe non-FN mode, or in alternative embodiments to change the way itresponds to queries broadcast from the commissioning tool searching forlamps 12 awaiting commissioning. By way of illustration, the followingexamples may be described in terms of the former implementation, wherethe FN mode controls whether or not the respective lamp 12 emits beacons(or at least whether it emits a certain type of beacon advertising it iswaiting commissioning). In the latter implementation, if thecommissioning tool 6 sends out an offer for an open network, thecontroller 26 of a master lamp will react to the offer but the slavelamp will ignore it.

Another property exploited by embodiments herein, is that a lampconfigured according to a ZigBee standard such as the ZigBee Light Linkstandard will automatically switch from the FN mode to the non-FN modewhen it joins a ZigBee network. Therefore according to embodimentsherein, causing a lamp to join and leave a temporary network can be usedto artificially manipulate the FN mode.

In accordance with exemplary techniques disclosed herein, the controller26 on each of the lamps 12 is configured to obey a distributedmaster-slave protocol whereby it determines in a distributed fashion(without involving coordination by a centralized controller) whether itis itself to become a master or a slave for the purpose of thecommissioning. The protocol is arranged such that one and only one lamp12 a per luminaire 4 will become master, and all the other lamps 12 b,12 c, 12 d in that same luminaire 14 will be slaves to the respectivemaster 12 a (N.B. the lamp labelled 12 a is described herein as themaster just by way of example—in general the master could be any of thelamps 12 a-d in the same luminaire 4). Techniques for detecting whichlamps 12 a-d are within the same luminaire will be discussed in moredetail later.

The controller 26 of the lamp 12 a that becomes master then artificiallymanipulates the FN mode of its slaves 12 b-d so as to hide all but themaster 12 a from being shown to the user 8 in the user interface of thecommissioning tool 6. This is achieved by having the master 12 a causethe slave lamps 12 b-d to join a temporary wireless (e.g. ZigBee)network created by the master. Further, the controller 26 of the masterlamp 12 a performs one or more commissioning operations on behalf ofitself and its slaves 12 b-12 d as a group. Thus from the user'sperspective, the commissioning is only performed for each luminaire 4,not each individual lamp 12, with the commissioning involved inreporting the identifiers of the slaves 12 b-12 d to the commissioningtool 6 and joining the slaves into a network being performed entirely“behind the scenes”.

The following describes an exemplary work flow for a situation in which,before the start of the auto-grouping, all TLED tubes 12 a-d within theluminaire 4 are newly installed, i.e. Factory New (FN). This isillustrated by way of example for a room with N fixtures 4 each havingfour TLED tubes 12 a-12 d, being commissioned into a ZigBee network.Where it is described in the following that a lamp 12 performs a certainoperation, it may be assumed that this is performed under the control ofits respective controller 26, using the respective wireless interface 28where appropriate.

Firstly, four times N factory new (FN) TLED tubes 12 are inserted into Nluminaire fixtures 4 respectively. Initially, each FN TLED 12 detects noZigBee network (or only a network or networks with below a thresholdreceived strength, which it can assume must be from another luminaire oreven another room—see the “bucketing” feature described later).

Every TLED 12 in the environment 2 then starts a new ZigbBee network,beginning in the FN mode (note: no bridge or remote controlcommissioning device 6 need present within the system at that time).This means each lamp 12 in the environment 2 transmits beaconscommunicating the fact that it is a new lamp searching for neighbours.These beacons include a unique identifier number (e.g. the 64 bit ZigBeeaddress of the TLED). All TLEDs 12 also listen for these beacons, andanalyse the addresses of the other TLEDs 12 versus their own address.The single TLED 12 a with the lowest address starts the second phase ofthe auto-commissioning by modulating its 64 bit ZigBee address onto theballast line connecting it to the ballast 10, by modulating the load itplaces on the ballast (to be discussed in more detail later). All otherTLEDs 12 check if the power they received from the ballast 10 is beingmodulated. If so, these TLEDs 12 b-d each grab the 64 bit address whichit has received via the ballast load modulation. This 64 bit address isthe ZigBee address of the master TLED 12 a in its own luminaire 4. Note,the lamps 12 may not all turn on and begin the process at exactly thesame time. Legally speaking the power of the luminaire 4 should be offduring re-lamping, so if this rule is followed the lamps will all beturned on together after re-lamping and hence begin the process at thesame time. In practice this rule is not always followed, butnonetheless, as long as the lamps 4 are configured to continue searchingfor potential masters or slaves for a certain finite window afterpower-up, the described process will still work.

An alternative approach for selecting a master would be to use a randomtimeout after powering-up the mains 16, before which each TLED 12 isallowed to start up its radio 28. The TLED 12 on which the radio 28 isfirst active becomes the master and starts up the network. The randomtimeout feature of the TLED tube 12 is disabled after a certain timeperiod, e.g. one month, if the TLED 12 is still un-commissioned. Thisrandom timeout approach is however less preferred: the process coststime, and in addition it is hard to dimension for both small and largenetworks (the larger the network, the longer the required start-up delaywill be). Whereas the load modulation works directly, and for anynetwork size.

By whatever means the master and slaves are chosen, each of the slaveTLEDs 12 b-d subsequently joins the ZigBee network of the ZigBee masterTLED device 12 a (causing each of the slaves to switch to the non-FNmode and stop beaconing). The master TLED 12 a notices one or more TLEDs12 b-d have joined its network. This network is used by the master 12 ato obtain unique numbers (e.g. 6-digit remote reset codes) from itsslaves 12 b-d, wherein these are used later on during the commissioningprocess to pull the slave TLEDs 12 b-d into the ZigBee network set up bythe installer remote (commissioning tool) 6.

After it has been determined which of the TLEDs 12 are located in thesame luminaire 4, the master TLED 12 a saves the unique address of itsslave TLED neighbours 12 b-12 d, along with network parameters and keys.The master TLED 12 a exits the network it created for its slaves 12 b-dand goes back to the FN mode so as to show up to the commissioning tool6 as awaiting commissioning. However, it leaves its slave TLEDs 12 b-din this newly created network, so that they will not show up to thecommissioning tool 6. Hence the master 12 a acts as the representativeof its slaves 12 b-d.

As the master 12 a has returned to the FN mode, this means it will startbeaconing again. To avoid it being taken into account in the distributedprotocol for selecting the next master, it therefore indicates in one ormore of its beacons that it has already acted as master.

Regarding the beaconing generally, the TLEDs 12 require a mechanism tocommunicate some unique ID, their presence, and whether they havealready been grouped per luminaire 4. Normal ZigBee beacons containamongst other things the extended PAN ID of their network, but do notprovide space or mechanism to include other information that the TLEDs12 may need to exchange. Therefore, one of the following alternativemethods may be used to indicate whether a master 12 a returning to theFN mode has already been a master (has already grouped the lamps 12 b-12d in its respective luminaire.

A first possibility is to use privately defined announcement messagesover ZigBee. According to this approach, each lamp 12 starts its ownZigBee network without being open for other devices to join thatnetwork. At one or more times throughout the commissioning process (asthe initial beaconing and/or later), each TLED 12 regularly (at somepredefined interval) sends on its own network an inter-PAN announcementmessage containing information relevant for the present purpose (e.g.MAC address, indication of being master vs. slave TLED within aluminaire, whether or not auto-grouping with slave TLEDs in theluminaire already happened). For the rest of the time, it listens oneither its own channel or all channels (see note below) for similarmessages from other TLEDs 12. Each factory new TLED listens to all suchmessages within its radio range, and acts accordingly (see rest oftext). If a TLED 12 has already performed the auto-grouping, it adjuststhe contents of its announcement message accordingly. Aftercommissioning is complete, sending the announcement messages may becontinued for use cases such as replacing one of the TLEDs (discussed inmore detail later).

The above could be performed with all TLEDs 12 on a ZigBee channel knownto them all (easiest since devices need to listen only on one channel),or each TLED could choose on a random ZigBee channel (which means eachdevice needs to listen on all channels—somewhat more involved but allowsa good spread over all ZigBee channels).

A second possibility is to use modified beacons. This is similar to thefirst possibility above, but instead of the announcement messages usinga beacon as defined in a ZigBee spec, the protocol byte is set to avalue different from the values used for existing systems (00=ZigBeePro, etc.) In the payload, the various information (same as described inrelation to the first possibility above) is carried.

A third possibility is to use alternative type of beacons other thanZigBee beacons, of another protocol other than ZigBee. This is avariation on the first and second possibilities above, but theinformation in question is transmitted in the alternative beacons, e.g.BLE (Bluetooth Low Energy) iBeacons.

By whatever means the first master 12 a indicates it has already been amaster, other TLEDs 12 in other luminaires 4 which are not yetauto-grouped then notice they no longer received beacons from the masterTLED 12 a in the first luminaire without this indication being given.This means another TLED 12 will now have the lowest unique number,assign itself the master role for its luminaire 4 and repeat the aboveprocess for this luminaire. The whole process repeats until a respectivemaster TLED 12 in every luminaire 4 has completed these steps.

Note: optionally, the process flow described above may be augmented byusing a measure of the received signal strength of the beacons, e.g. areceived signal strength indicator (RSSI), in order to help select tubeneighbours 12 b-12 d within the luminaire 4 by detecting those having ahigh enough signal strength. That is, the RSSI can be used to speed upthe TLED auto-commissioning process. Beacons with an RSSI below apredetermined threshold can be ignored so that multiple luminaires 4(e.g. in a large open-plan office) can run the above auto-groupingprocess at the same time, independently verifying which TLEDs 12 areindeed housed within the same luminaires 4. RSSI alone is notnecessarily reliable enough for identifying the TLEDs 12 residing withinthe same luminaire 4 with sufficient certainty. Hence, in embodimentsthe RSSI is only used to create RSSI-based buckets of TLEDs 12 (i.e.candidate subsets), e.g. those that are likely to be in the sameluminaires, or those that might be in the same luminaire. Based on thebuckets, a second identification mechanism is then used—for instanceshorting the electric load of one master TLED 12 a and detecting theballast load change at another slave TLED 12 b-d within the luminaire—tomore reliably determine which TLEDs 12 are indeed housed within the sameluminaires 4.

In the next phase of the commissioning flow, the installing user(person) 8 gets involved in the commissioning. The installing user 8sees on his commissioning tool 6 only one FN lamp 12 displayed perluminaire 4 (i.e. the master TLED). If the user 8 wishes to include theluminaire 4 of one of these visible, FN lamps 12 a in the network he orshe is creating, then he or she selects that lamp 12 a in the userinterface of the commissioning tool 6. This causes the commissioningtool 6 to send a commissioning request to the selected lamp 12 a. Inresponse, this lamp 12 a provides a visual indication to the user 8,e.g. by flashing its lighting element 18. The user 8 can thus see thatthe lamp 12 a that he or she selected is indeed in the luminaire 4 thathe or she intends to commission. If so, the user confirms this via theuser interface of the commissioning tool 6, causing the commissioningtool 6 to include the master TLED into its ZigBee network (i.e. thewider ZigBee network being created for the purpose of controlling thelamps 12 in the subsequent operational phase). The master TLED 12 a alsotells the commissioning tool 6 about its three non-FN TLED slaves 12 b-d(including their unique IDs, e.g. ZigBee addresses). The slave TLEDs 12b-d then join the ZigBee network set up by the commissioning tool (or alighting bridge). There are at least three options for this.

A first option is for the commissioning tool 6 to use the slave TLEDs'unique IDs to pull the slave lamps 12 b-d into its network using 6-digitreset codes. These can be broadcast by the commissioning tool 6 to makethe slave TLEDs 12 b-d become FN again and join the commissioning tool'sremote network.

As a second option, the master TLED 12 a temporarily goes back to theold network (the network it created with its slaves 12 b-d) and usesthis to transmit to its slave TLEDs 12 b-d the parameters of the newnetwork (the network being created by the commissioning tool 6). Theslave TLED tubes 12 b-d then switch to the new network, and the masterTLED tube 12 a also goes back to the new network of the commissioningtool 6.

In a third option, the commissioning tool 6 instructs the master TLED 12a to send a “remote reset” to its slave TLEDs 12 b-d. The master TLED 12a temporarily goes back to the old network and transmits a “remotereset” to its slave TLEDs 12 b-d, causing the slave TLEDs 12 b-d tobecome FN again. The master TLED tube 12 a then goes back to the networkof the commissioning tool 6. The commissioning tool 6 searches for newdevices and finds the three slave TLEDs 12 b-d.

Thus the master and slave lamps 12 a-d are all collectively pulled intoa wireless network (e.g. ZigBee network) created by the commissioningtool 6, so that the lamps 12 a-12 can subsequently be controlled viathat network in the operational phase. Whatever option is used,preferably the commissioning tool 6 also assigns a group address (e.g.ZigBee group address) to the lamps 12 a-12 d in the same luminaire 4(allocating a different respective group address to each respectiveluminaire). This group address then allows the controlling device (notshown) to control the lamps 12 a-d together by broadcasting one or morecontrol messages each with only a single group address as thedestination address (rather than transmitting a separate message to anindividual address of each lamp). For example, according to ZigBeemessages can be broadcast with a group identifier, whereby only lamps 12containing this identifier (i.e. being in this group) will react. Whenassigned, the commissioning tool 6 communicates the group address to themaster 12 a and each of the slaves. In the operation, each lamps 12 a-12d then listens for any messages with the group address, and reactsaccordingly. Note however that having a group address for all TLEDswithin a luminaire is not necessarily required. Alternatively, once thecommissioning process is finished, it is possible to simply address eachTLED by its own individual address.

The above thus describes a mechanism by which an arrangement of newlyinstalled luminaires 4 can be commissioned. A further situation in whichthe auto-grouping may be used is when one of the individual TLEDs 12 ina given luminaire 4 is replaced, at a later time after the initialcommissioning phase is over and the operational phase has begun. Thefollowing describes a work flow for the replacement of one of the non-FNTLEDs tubes 12 in a luminaire 4. This connected TLED field-replacementaims at “out-of-the box” auto-commissioning of a replacement TLED 12without involvement of a remote control or a commissioning expert. Theauto-grouping process can be triggered by the combination of a factorynew connected TLED tube 12 and power-cycling of the mains voltage 16once via a switch. Alternatively, the re-lamping person may activelytrigger the auto-commissioning for the replacement tube (e.g. five timesmains-switch toggling within 10 sec).

The auto-commissioning of the replacement TLED proceeds as follows. Thenewly installed TLED, e.g. a replacement for 12 b, sends a signal to theballast 10, by modulating the load it places on the ballast 10. OtherTLEDs 12 a, 12 c, 12 d in the same luminaire 4 hear this message in thepower supplied to them by the ballast 10. One of these TLEDs 12 a, 12 c,12 d opens its network (e.g. the one with the lowest unique address, orthe TLED 12 a which already became the master of the luminaire 4). Thenew TLED then joins the network. The master TLED 12 a programs theappropriate ZigBee groups in the new TLED so it functions in the sameway as the replaced TLED 12 b.

This assumes that the commissioning tool 6 has allocated all TLEDs 12a-d in a luminaire 4 to a single ZigBee group. Having all TLEDs 12 a-dwithin a luminaire 4 in the same group is very advantageous for thisreplacement use case, as then the Zigbee group number of the remainingold TLEDs 12 a, 12 c, 12 d can be directly re-used for the newreplacement TLED. Unlike Zigbee group addresses, normal ZigBee addressesdo not have this characteristic: the new replacement TLED would alwayshave a different 16-bit address than the old one.

The above mechanism may include a timeout in case no-one answers therequest. Or as an alternative, the new TLED may send a request for anetwork over ZigBee, which is monitored by the other TLED(s) 12 a, 12 c,12 d—or at least the master 12 a of the luminaire 4—and answered. Alsohere, signaling via the ballast line can be (and preferably is) used toverify that both are in the same luminaire 4. For TLED fieldreplacement, this verification as to whether an “aspirant” wireless nodewanting to join the lighting network is indeed connected to afluorescent tube ballast 10 also serves as a security mechanism—it canonly join if it is physically in the same luminaire 4 as an existingmember 12 a of the network, thus avoiding rogue devices joining formalicious purposes such as in an attempt to disrupt the lighting.Sharing the same fluorescent tube ballast 10 is in several ways the TLEDmarket analogy to the touchlinking mechanism used for consumerapplications. In consumer applications, the pairing procedure requiresphysical proximity for remote controls with the bulbs to prevent pairingof malicious new network components to the lamps e.g. from outside ofthe housing 14. In the same way, embodiments of the present disclosureenable an existing lamp 12 a to assess the authorization of the newZigBee component to join the network, by verifying that the new wirelesscomponent purporting to be a TLED is indeed wired on the same ballast 10as the existing connected TLED 12 a and hence indeed is a replacementTLED and not another malicious wireless device.

To summarise the above, FIG. 9 gives a state diagram showing thedifferent possible states of a lamp 12 in accordance with embodiments ofthe present disclosure. Every lamp begins life, when powered up forfirst the first time, in an “out of the box” state 54 where it performsthe distributed negotiation protocol to determine whether to become amaster or slave, as discussed above. Then, based on this, one of thelamps 12 a transitions to the master state 56 while the others of thelamps in the same luminaire each transition to the slave state 58. Whilethe first lamp 12 a is in the master state 56 and the second lamp 12 b-dare in the slave state 58, the master 12 a interacts with thecommissioning tool on behalf of the first and second lamps 12 a-dcollectively, in order to initiate one or more steps to commission thoselamps 12 a-d as a group. Finally, after commissioning is over, both themaster and slave lamps 12 a-12 d transition to the operational state(operational phase) 60 where they are usable for their ultimate purpose,i.e. to be used to illuminate the environment 2, and be controlled viathe ZigBee network or other such wireless network established by thecommissioning tool (e.g. to be dimmed, used to set colour lightingscenes, etc.). In the operational state 60, each lamp 12 monitors forsignals for potential replacement lamps as discussed above.

Note that whether (a) the lamp is FN (“Factory New”) mode is a separatevariable than whether (b) it is in the “out of the box”, master, slave,or in the final operational state. This can be seen by considering thatwhile a lamp is master, it switches between both FN and non-FN, and alsowhile a lamp is a slave it can also switch between FN and non-FN—so (a)and (b) are separately controllable factors. Thus techniques disclosedherein involve deliberately and artificially manipulating the FN stateso that it does not just indicate whether newly “out of the box”, but isused for an extra purpose of controlling which of multiple lamps 12 inthe same luminaire 4 appear to the commissioning tool 6.

The use of load-modulation to signal via the ballast may be particularlyadvantageous compared to RSSI-only-based auto-grouping. In the USA forinstance, luminaires always have a continuous metal enclosure for boththe upper top and the sidewalls of the luminaire 4. The metal side-wallsof the luminaire block the direct wireless path (in the same plane)between the TLEDs 12 being housed in different luminaires 4.Consequently, the wireless attenuation between TLEDs 12 housed in twodifferent luminaires 4 is typically stronger than for two adjacent TLEDsat 15-20 cm distance housed within the same luminaire 4. However, forsmaller than usual installation distance between adjacent luminaires 4,the attenuation caused by the luminaire metal sidewalls will be undercertain cases insufficient to prevent accidental auto-grouping ofconnected TLED tubes 12 from different luminaires (e.g. if a punch-outhole in metal sidewall of luminaire is located right next to the TLED'sradios 28). In addition, each of the TLED tubes 12 may have its radio 28located in only one of the end-caps 20 i of the tube 12. Hence, therewill be a 50% likelihood that two neighbouring TLED tubes 12 a, 12 blocated within the same luminaire 4 will be mounted by the installerwith the radio 28 at opposite ends of the tubes 12. Placing the antenna28 in the middle of the TLED may overcome this problem. However, from aTLED hardware perspective, the preferred radio location in a connectedTLED is within the end cap 20.

To ensure sufficient robustness, it is therefore preferable to “bucket”the TLEDs 12 with the help of RSSI, and then use a second groupingmethod to determine with certainty which TLEDs 12 are located within thesame luminaire 4.

There are at least two options for the second auto-grouping method. Oneembodiment, as mentioned above, is that the master TLED 12 a tubesignals via the ballast 10 by modulating the load it places on theballast 10 (e.g. to signal its unique ID). The other TLEDs 12 b-d arethen looking to detect the load transitions caused by their sister TLEDswithin the same luminaire 4. This will be discussed in more detailshortly.

As an alternative embodiment however, each of the connected TLEDs 12 mayhave an integrated light sensor which can be used to allow the slaves 12b-d to detect a light modulation pattern emitted by the master TLED 12 alocated within same luminaire 4 (and/or the slaves 12 b-d could emit alight pattern to be detected by the master 12 a). The light sensor maybe a pre-existing daylight sensor, or a dedicated light sensor for thepurpose of the disclosed detection. The master 12 a will selectivelyswitch off the light within the luminaire 4 to aid the master TLED tubeto receive coded light messages from its neighbours 12 b-d withoutdisturbance from its own light. Coded light can be used to detect whichlamps 12 are in the same luminaire because the housing 14 of theluminaire 4 acts to at least partially block coded light signals—solamps 12 a-d in the same luminaire 4 will receive each others' signalsbut not those from lamps 12 in other luminaires 4. To facilitate this,the light sensors and/or positions of the lamps 12 may be specificallyarranged so that the light sensor of a given lamp 12 in a givenluminaire 4 only, or at least predominantly, receives light from lampsin the same luminaire 4. E.g. the light sensor may be arranged to faceupwards to detect the light reflected from an upper reflective elementin the interior of the respective luminaire housing 14. A similarprinciple could even be applied using other media as the means by whichto detect whether lamps 12 are in the same luminaire: e.g. each lamp 12may emit an ultrasound signal that is blocked by the housing 14, or eachlamp 12 may emit a radio signal which is blocked by metal elementsaround the sides of the luminaire housing 14 (such that signals can bereceived from a controller or commissioning tool 6 below the luminaire4, but not from other luminaires mounted on the same ceiling).

As an additional feature, in embodiments, by using the light sensor perTLED 12 it is possible to identify the relative positioning of the TLEDtubes 12 a-d within the luminaire 4. This enables directional lightingsweeps across the four TLEDs 12 a-d within the luminaire 4 (from left toright, or from right to left). This dynamic swiveling light beam maymake it possible to identify the directionality among neighboringluminaires 4, which may enable auto-commissioning at room level In thisapproach, the TLEDs 12 housed within the same luminaire 4 sequentiallyswitch on their light from left side to right side of the luminaire. Atthe same time, the LEDs of the TLEDs in the neighbouring luminairesremain switched off, but detect with a light sensing means the light luxlevel on the floor caused during the sequential switching on of the TLEDtubes within the neighbouring luminaires. The physically closer thelighted-up TLED tube is to the receiving TLED, the more light will be onthe floor. Based on the detected the lux level on the floor during thestep-wise switching of the tubes, the TLED tube (in light off mode) candeduce whether the neighbouring luminaire performing the sweeping lightis actually located on its right or its left side

The following now describes an exemplary implementation of the techniquefor intentionally modulating the load placed on the ballast 10 by themaster 12 a, in order to signal a pattern in the power supplied by theballast 10 to the lamps 12 a-d in the same luminaire 4.

As discussed, a fluorescent luminaire 4 typically takes several TL tubes12 a-d wired to one single ballast 10. A typical wiring diagram for aninstant start (IS) ballast 10 is shown in FIG. 4. At each end of the TLtube 12, the two pins 22 are shorted by a shunted lamp holder. The pins22 a,i at one end of a first of the lamps 12 a in the luminaire 4 areconnected to the ballast 10 via a first blue line 30 a, and the pins 22b,i at one end of a second of the lamps 12 b are connected to theballast 10 by a second blue line 30 a (and so forth if there are morethan two lamps in the luminaire). At the other end, the pins 22 a,ii and22 b,ii (etc.) are all connected together and connected to the ballast10 via the same red line 32. The ballast 10 itself is connected to themains 16 via the black line 34 and white line 36.

FIGS. 5 and 6 show examples of different types of ballast 10 forpowering fluorescent tubes. By way of example, these are the dominanttopologies in NAM regions for Instant Start (IS) ballasts, namely theself-oscillating (SO) circuit (see FIG. 5) and current-fed half-bridgeresonant circuit (see FIG. 6).

FIG. 5 shows a typical High Frequency (HF) fluorescent ballast. Thisballast 10 consists of an EMI (electromagnetic interference) filter 38arranged to receive the upstream mains power supply 16, and to filterthis to produce a filtered power supply and to block the interferencegenerated by the ballast back to the mains. The ballast 10 alsocomprises a PFC (power factor correction) input stage 40 connected toreceive the filtered power supply from the EMI filter 38, and to performa power factor correction on the filtered power supply in order toproduce a power factor corrected power supply. The circuit furthercomprises a resonant output stage 42 connected to receive the powerfactor corrected power supply from the power factor correction stage 40.This circuit works in self-oscillating mode in order to generate, basedon the received power factor corrected power supply, the final powersupply as used to power the fluorescent tubes (or their TLEDreplacements 12). The two transistors in the resonant circuit 42 aredriven by the auxiliary winding of the transformer T1. The output istypically isolated from the mains 16. The ballast 10 thus generates a HFvoltage of about 600V across the secondary winding of T1. Capacitors C1and C2 are connected in series with each of the lamps 12 a, 12 brespectively. The capacitors C1, C2 act as a ballasting element andcontrol the lamp current.

In recent products, the half-bridge (HB) resonant circuit has becomemore popular due to its cost saving. A typical HB fluorescent ballasttopology is shown in FIG. 6. This circuit is similar to that of FIG. 5,but with the SO resonant circuit 42 replaced with a HB circuit 44. TheHB circuit 44 is typically controlled by an integrated circuit (IC). Theoutput is not isolated from the mains 16.

Details of some exemplary techniques for transmitting and receiving asignal via ballasts 10 such as those shown in FIGS. 5 and 6, or others,are now described in more detail in relation to FIG. 7.

FIG. 7 shows an example lamp 12 for performing load modulation in orderto signal via the ballast 10, and also to detect such signals from otherlamps 12 via the power supply received from the ballast 10. Inembodiments, each of the lamps 12 in one, some or all of the luminaires4 may be configured in accordance with FIG. 7.

As shown in FIG. 7, the lamp 12 comprise a rectifier 23 comprising anarrangement of diodes D1, D2, D3, D4 arranged to receive an AC powersupply from the ballast 10 via the pins 22 of the lamp 12, and toconvert this to DC power. Various forms of rectifier are in themselvesknown to a person skilled in the art and the rectifier 23 does notnecessarily have to take the form shown in FIG. 7 (though it may welldo). The lamp 12 further comprises an LED driver 24 arranged to receivethe DC power from the rectifier 23, and based on this to generate aconstant or approximately constant current to the LED-based lightingelement 18 (LED string or array). Note however that a constant current,as referred to herein, does not necessarily mean the current is notadjustable. Rather, the lamp 24 comprises a controller 26, e.g.comprising a microcontroller 46 arranged to execute embedded firmware ofthe lamp 12. Further, the lamp 12 comprises a wireless interface 28,e.g. ZigBee, Wi-Fi, 802.15.4 or Bluetooth interface (the above has beendescribed primarily in terms of the ZigBee example). The microcontroller46 is connected to the wireless interface 28 and to the LED driver 24.It is arranged to receive messages via the wireless interface 28, e.g.originating from a lighting controller or one or more wireless sensors(not shown), and based thereon to determine a light output level withwhich the lighting element 18 is to emit light. The microcontroller 46then indicates this light output level to the LED driver 24, and inresponse the LED driver 24 sets the current to the appropriate level toachieve the desired light output. The current supplied by the LED driver24 is therefore constant in that for a given light output indicated bythe controller 26, the LED driver 24 ensures that the current isapproximately constant. Also, note that in the case where pulse widthmodulation (PWM) dimming or such like is used, the constant currentrefers to the average current. Further, in embodiments, the LED-basedlighting element 28 may comprise differently coloured, independentlycontrollable LEDs or subarrays of LEDs. In this case the controller 26and LED driver 24 may also individually set the output levels of eachthe differently-coloured LEDs or subarrays in order to control thecolour of the light output.

In order to signal via the ballast 10, the internal controller 26 of thelamp 12 further comprises transmitting circuitry in the form of atransistor switch M1, connected so as to be able to modulate the loadplaced on the ballast 10 by the respective lamp 12, under the control ofthe microcontroller 46. In the example embodiment shown, this isachieved by connecting the source and drain (or collector and emitter)of the transistor M1 in parallel across the load, e.g. across the LEDdriver 24 or lighting element 18, with the gate (or base) of thetransistor M1 being connected to the controller 26. This allows thecontroller 26 to selectively short out the load by controlling the gate(or base) of the transistor M1. When it does so, this causes a“hiccough” to be fed back through the ballast 10, which is detectable inthe power received by the other lamps 12 in the same luminaire 4. Bycontrolling the shorting according to a suitable, predetermined code(see below), it is thus possible to signal to other lamps 12 in the sameluminaire 4 via the ballast 10.

To be able to sense such signals from other similar lamps 12 in the sameluminaire 4, the lamp 12 of FIG. 7 further comprises a sensing circuit50 connected between the rectifier 23 and LED driver 24 (though it couldpotentially be connected in other parts of the circuit). This circuit 50is configured to detect the signalled pattern of “hiccoughs” in thepower supplied by the ballast 10, and to supply the detected signal tothe controller 26 for decoding. The sensing circuit 50 may be configuredto sense the modulations in the received power by sensing modulations inthe current, voltage and/or frequency of the received power. E.g. inembodiments, the sensing circuit 50 is a current sensing circuit.

Thus the controller 26 can transmit signals via the ballast 10 and alsoact on such signals according to the various commissioning flow stepsdisclosed herein, in order to perform the auto-grouping of the lamps 12a-d in the same luminaire 4.

To begin the TLED grouping method, one master TLED lamp 12 a (e.g. outof a bucket of TLEDs likely sharing the same luminaire 4) initiates theauto-grouping process. During the auto-grouping process this master TLEDlamp 12 a starts the LED load shunting process, and opens and closes theswitch M1 at a predefined frequency and duty cycle (as determined by themicrocontroller 46). Each of the slave TLED lamps 12 b-d senses thechange in the lamp current via its internal current-detection unit 50.When the master TLED lamp 12 a performs this coded shunting action, theloading condition of the ballast 10 changes and the ballast deviatesfrom its normal operating point. Consequently, the remaining TLED lamps12 b-d in the group receive either more or less power from the ballast10. The magnitude and direction of the change depends the fluorescentballast topology, but in any case a change will be a noticeable to theslave TLED 12 b-d. The slave TLED lamps sense this change by the meansof the detection unit 50 inside the lamp. Because the ballast 10 is acurrent source, the coded shorting performed by the master TLED 12 alamp is a safe action and will not damage the ballast 10 or any of theTLED lamps 12 a-d.

The load shorting functionality can be implemented at low cost within aTLED 12, e.g. with a shunt switch M1 as illustrated in FIG. 7. In eachTLED 12, an instance of this shunt switch M1 is placed after therectifier 23 (this switch M1 may in fact already be present in existingTLEDs 12 for pulse width modulation dimming purposes). When M1 closes,the lamp input is shorted and the current from the ballast 10 isbypassed without delivering power to the LED load 18. For detecting thecodes sent by other TLEDs 12, an instance of the current detection block50 is inserted into the main current loop of each TLED lamp 12. Thecoded changes in the ballast current and frequency are sensed via thisdetection block 50, and the extracted signal is fed to the on-boardmicrocontroller 46 within the TLED 12. The same microcontroller 26 alsocontrols the shunt switch M1.

Note that in embodiments, filament circuitry 52 i, 52 ii may be includedat the inputs 22 i 22 ii on the two sides of the TLED 12 respectively,in order to emulate the filament of a real fluorescent tube lamp. Thiscircuitry 52 may for example be a power resistor, or may be left openfor instant start ballasts. The filament circuit 52 hence will pass thesignalled codes without any impact on the signal.

FIG. 8 illustrates an example shape of the ballast current I in the timedomain t (after conditioning) as received by a slave lamp 12 b-daccording to embodiments disclosed herein. The top sketch shows thecurrent during normal operation, whereby the ballast current received bythe slave TLED 12 a-d is at a stable level. The master TLED lamp 12 athen starts with the grouping process and forces a coded pattern ontothe ballast 10. Consequently, as illustrated in the bottom sketch ofFIG. 8, the current received by the slave TLED 12 b-d contains amodulated signal pattern with the frequency equal to the shuntingfrequency of the master lamp. The shunting frequency can be for instancein the 1-10 Hz range, or in the range of a few hundred Hz to a few kHz(preferably the mains frequency is avoided to minimize unwantedinterference by the mains frequency components).

There are several ways for the current detection unit 50 to detect thecoded modulation pattern. In a first option, the detection is done bysensing the change in the average current value. First the sensed signalis averaged via a low-pass filter. Then the value is read by themicrocontroller 46 and compared to the nominal value. Themicrocontroller 46 then decides if this represents a signal from anotherlamp 12 sharing a common ballast 10 with its own respective lamp 12.E.g. each slave lamp 12 b-d may listen on the ballast 10 for a signalfrom the master 12 a identifying the master, and if the slave 12 b-ddetects this, the respective slave 12 b-d replies to the master 12 a viathe wireless interface 28 to inform the master 12 a of the slave'sidentity (e.g. address). Or operating the other way round, the master 12a may listen on the ballast 10 for signals received from the slaves 12b-d identifying themselves to the master 12 a over the ballast 10.

As a second, alternative or additional option for the detection, thedetection may be done by measuring the frequency of the receivedmodulations. If required, the master TLED lamp 12 a can even send somebasic message to the slave lamps 12 b-d by modulating the frequency,duty cycle, etc. This second option is more accurate than the firstoption above, since different ballast circuit topologies result indifferent modulation depths of TLED current. The average value detectionmethod used by the first option is therefore more prone to errors thanthe second option (though not necessarily unusably so).

Regarding the coding scheme used to signal information via the ballastload modification scheme disclosed above, various coding schemes arepossible. For instance, the ballast-based communication channel betweenmaster and slave TLEDs 12 a-d may utilize a binary coding scheme such asMorse code, Manchester coding, or pulse position modulation, etc. Theinformation signalled may comprise some or all the transmitting lamp's64-bit unique ZigBee address (or other unique identifier), optionallyalong with some other bits such as header bits, start and stop bits,and/or possible error detection or correction bits. In certainembodiments, this communication channel may also allow for sendingadditional information, e.g. via the addition of a byte of “opcode”. Theslave lamps 12 b-d may be enabled to acknowledge to the master 12 b-dthat they have received the signal, either back via the ballast 10 orvia the wireless interface 28. After the signalling, the master 12returns to the FN mode and engages with the commissioning tool 6 asdiscussed previously.

Note that the signalling over the ballast 10 could also be implementedvia modulating only a portion of the luminance range (e.g. between 100%and 80% light output) rather than full 100% to 0% (light off) modulationof the LEDs 18. Similar to coded light type coding, this 100%-80%modulation may be even utilized later in the operational phase forballast-load-change based ‘side channel’, which is invisible to the enduser during normal lighting operation.

After completion of the auto-grouping, both the master and slave TLEDlamps 12 a-d cannot be controlled until they have been commissioned bythe installer 8. There a several options as to which light levels tochoose during the state where the TLEDs 12 a-d are auto-grouped but notyet commissioned. In one embodiment, the master lamp 12 a and slavelamps 12 b-12 d are automatically set at different light levels toenable a quick visual check for the (first) installer 8 as to whetherthe auto-pairing was done correctly.

Bearing in mind the various mechanisms discussed above by which a lampcan detect and communicate with another lamp in the same luminaire, thedisclosure now returns to further possibilities for re-lamping.

Re-lamping is the process of replacing a wirelessly networked lamp at alater stage after the lamps have already been commissioned. This raisesnot only the problem of how to enable the replacement TLED (or othersuch wireless lamp) to be put in network, but also how to determinewhich of the existing luminaire-groups of TLEDs the replacement TLEDbelongs to. As mentioned, there do exists “self-healing” networks inwhich a node is replaced by another node, but these do not have theconcept of logical subgroups (sub groups of the total set of nodes inthe network).

According to further aspects disclosed herein, a solution to the can beenabled based on any of the above techniques such as load modulation, ora coded light, heat, audible-range sound or ultrasound signal that isblocked by the housing of the luminaire 4. The following operations canbe assumed to be performed by the controller 46 of the respective lamp12, communicating via the relevant communication interface(s) 10 and/or28 as appropriate.

When a new lamp becomes available to join the network, this can also bedetected by the one of the lamps 12 a. A similar protocol as discussedabove in relation to commissioning can be used to choose which of thelamps 12 a, 12 c, 12 d does this, i.e. which becomes the master for thepurpose of the re-lamping process. In embodiments, the new lamp emits aradio beacon indicating it is not currently connected (e.g. indicatingthe new lamp is in the ZigBee FN mode), and this is detected by themaster lamp 12 a in each luminaire 4 (or at least one or some of them).Alternatively or additionally the master 12 a could repeatedly (e.g.periodically) emit beacons polling for new lamps. This beacon may be viathe same wireless radio network that the new lamp is trying to join, ora different radio access technology. Alternatively the new lamp couldsignal to the master lamp 12 a, or be polled via the master lamp 12 a,via another communication means such as coded light (in the visible orinvisible range), ultrasound, or even audible-range sound, or the loadmodulation discussed above. E.g. when the new lamp is plugged in to theluminaire 4 (but not yet connected to the network), it modulates asignal onto the ballast 10 by modulating the load it places on theballast, and this is detected by the master lamp 12 a in a similarmanner to that discussed above. As another example the master lamp coulddetect the presence of the new lamp by means of a near-fieldcommunication (NFC) technology, such as an RFID tag in the new lamp.

Further, when an old lamp 12 b is removed from the network, one of theremaining lamps 12 a can detect this because it has access to a tablestoring a list of its peer lamps 12 b-12 d that were housed in the sameluminaire (this list). Again the remaining lamp 12 a that does this maybe the master lamp chosen according to the above protocol. The list ofpeers 12 b-12 d could be stored locally on a memory of the master lamp12 a, or the master lamp 12 could be arranged to access it from another,remote device such as a server. This list is available because it wascompiled at the time of commissioning, preferably based on one of theauto-commissioning techniques discussed above, but potentially it couldinstead have been compiled manually by a more conventional commissioningprocedure.

When the master lamp 12 a detects a new lamp available to connect to thewireless network, the existing lamp 12 a can attempt to communicate withthe other lamps 12 a-12 d it expects to find in the same luminaire 4based on the pre-stored list. This attempted communication may be viathe ballast 10 using the load modulation discussed above. Alternativelythe attempted communication could be via coded light (in the visible orinvisible spectrum), acoustic signalling (ultrasound or evenaudible-range sound), near-field communication (NFC). or simply via thewireless radio network that the new lamp is trying to join, or anotherwireless radio technology. As long as the master lamp 12 a knows whichlamps it expects and has some means of communicating with the remaininglamps 12 c, 12 d in the luminaire 4, it can determine the fact that oneof the lamps 12 b is missing by the fact that no reply is received.

Because the master lamp 12 a detects both that there is a new lamp andthat one of its luminaire's previous lamps 12 b has gone, the masterlamp 12 a can therefore make a pretty good guess that the new lamp is areplacement for the old, and therefore automatically allocates to thesame subgroup (e.g. ZigBee group address) as the old lamp 12 b. Thuswhen a control message is received from a remote control device (e.g.lighting control app running on a smartphone or tablet), addressed tothe subgroup of a particular luminaire (e.g. same ZigBee group address),then the replacement lamp reacts accordingly along with the other,existing lamps 12 a, 12 c, 12 d in the same luminaire 4. Alternativelythe master lamp 12 a may send a message to the remote control deviceinforming it that the new lamp is to be allocated to its subgroup, sothe remote control device knows that when a user selects to control theparticular luminaire 4 in question, it should send the relevant controlmessage to each of the existing lamps 12 a, 12 c, 12 d and thereplacement lamp in the respective subgroup. Alternatively oradditionally, the master lamp 12 a may send a message to the remotecontrol device informing it that the new lamp is to be allocated to itssubgroup, and the remote control device uploads this information to bestored on a server (comprising one or more server units at one or moregeographic sites). Thus the asset management information that the newlamp is housed in this specific luminaire is available in the cloud.This enables for instance targeted replacement of tubes nearing theirend-of-life or—if there is a safety recall on the tubes—to exactly knowin which luminaire which new tube is installed.

Preferably, the above guess is improved by taking into accountproximity. Consider there are in fact two or more new, unknown nodesmaking themselves available to join the network, and/or two or moreluminaires 4 each having a missing lamp 12. In that case the solutionbased only on detecting new and missing lamps is ambiguous. If thedetection process is relatively fast compared to the speed at which auser can replace the bulbs, and the user removes and replaces them oneat a time, then this problem does not occur. Nonetheless, to improve therobustness of the process against such a situation, in embodiments anadditional criterion is added: the master lamp 12 a looks at some testof the proximity of the new lamp to the master lamp 12.

In embodiments, this could be based on different tests using differenttypes of signal. In one embodiment, the test is whether the new lamp canbe detected to be in the same luminaire based on the modulation of theballast power supply, along similar lines discussed above. That is, ifthe master lamp 12 a sees a signal from the new lamp in the power itreceives from the ballast 10, then it can tell that the new lamp is inthe same luminaire; whereas another master lamp in another luminairewould not detect this signal even though it may detect a radio (e.g.ZigBee) beacon from the new lamp, and hence can tell the new lamp is notpart of its respective luminaire 4. A similar approach can also be usedbased on coded light or ultrasound signals where the signal is at leastpartially blocked by the housing of the luminaire 4 (i.e. only themaster lamp 12 a in the same luminaire 4 will receive the light and/orultrasound signal from the new lamp, or at least only the master lamp 12a will do so with above a certain threshold signal strength).

In an alternative embodiment, the test of proximity could be based onmeasuring the received signal strength (e.g. RSSI) or time-of-flight(ToF) of a signal received from the new lamp. This could be a radiosignal (e.g. the same beacon by which the new lamp advertises itself asavailable to the new network), or could alternatively for example be acoded light signal in the visible or invisible spectrum (IR or UV), oran ultrasound signal or even audible-range sound signal, or a heatsignal (e.g. using an infrared sensor detecting the heat of a sub-partof the TLED such as the electronic driver).

In such cases each master lamp 12 a having a missing companion in itsrespective luminaire takes a measurement of the RSSI or ToF of thereceived signal, and these are compared with one another. The masterlamps 12 a from the different luminaires 4 may then be arranged toexchange measurements and each master 12 a performs the comparisonlocally, or a protocol could be implemented to determine which masterfrom which luminaire 4 should defer to the other, or both (or all) ofthe relevant masters 12 a could be arranged to submit them to anothercentral device such as a server or the remote control unit to becompared there. In such cases, the RSSI or ToF corresponds to anestimated radius of the new lamp from each master lamp 12 a, and so thecomparison indicates which of the master lamps 12 a the new lamp isphysically closest to. This master 12 a then allocates the new lamp toits respective subgroup, and each of the other masters repeats theprocess to continue looking for the replacement to the missing lamp inits own luminaire 4.

As a variant of the above, each master lamp 12 a may measure the RSSI orToF, compute the distance, and then compare this to a predeterminedthreshold (or the measured RSSI or ToF could just be compared directlyto a simple threshold of signal strength without converting todistance). In this case there should be no need to compare themeasurements obtained by different masters, an instead each simplycompares to its own local threshold. As long as the thresholds are thesame or at least do not overlap, there will be no ambiguous result.

Further, in equivalents to any of the above approaches, the new lamp maymeasures the RSSIs or ToF of signals it receives from the existing lampsand report these to the master lamps 12 a to perform the comparison. Orthe new lamp could even perform the comparison there based on signals(e.g. beacons) from different existing lamps 12 to decide which one isclosest, and report the result of the comparison back to the master 12a.

Note also that above of the above approaches based on received signalstrength or ToF measurements could also take into account correspondingmeasurements information from other lamps 12 c, 12 d in the sameluminaire 4 and/or from neighbouring luminaires to help to moreaccurately determine spatial proximity.

In yet another alternative embodiment for testing proximity, the testcould be based on a near-field (NFC) communication technology, such asan RFID tag included in the replacement lamp that can be detected by theexisting master. I.e. if the new component is contactable via NFC, itmust be in the same luminaire (this assumes the initial detection of thenew lamp was not via NFC, otherwise it is redundant to do an additionalstep of checking proximity using NFC).

Some more detailed examples of some example implementations are givenbelow.

In a first example, if the still-alive TLED 12 a detects presence ofunknown TLED (e.g. factory new TLED), the still-alive TLED scans networkfor its known group mates 12 b-12 d. If it did not find one of its groupmates, then the new TLED is likely part of that group; the still-aliveTLED opens up a networking group and provides both network settings andgroup settings to the replacement TLED. While the prior self-healingmesh network of U.S. Pat. No. 8,982,754 may perform and auto-joining ofreplacement components at general network level, the process disclosedherein additionally does so on a sub level to enable application-levelgrouping, based on the fact that each of the TLEDs has knowledge of itslocal group mates.

A second example begins the same as the first example above (i.e.identify differences between the initial install of the smart TLED andthe “as is” TLEDs still alive at this moment in time). In addition, thesecond example further use a proximity determination element. When areplacement TLED gets powered up, a search gets triggered to identifythe physically closest nodes wherever a smart TLED component is missing.This enables multiple replacement TLEDs to be installed at the same timeand still be grouped with the right TLED group (with its sister TLEDs inthe same luminaires). In most practical cases moderate accuracy oflocation process is already sufficient to allocate replacement TLEDs tothe right luminaire (e.g. in an open plan office). Currently achievablelocalization resolution is typically 1-2 m (e.g BluetoothLow Energybeacons such as iBeacons by Apple), which is larger than distancebetween neighboring luminaires. One alternative variant of this secondexample is to determine if replacement TLED is located within the samephysical luminaire 4 enclosure as the failed TLED on the basis it iscontactable via the same ballast 10, or via some other channelconstrained by the physical limits of luminaire 4 such as a light,ultrasound or even radio channel that is shielded by some or all ofluminaire's casing 14.

Conventionally, an installer would have to add a new lamp by telling—viaa remote control held by the installer—the parent luminaire to open upthe network (i.e. allow new lamp to exchange network parameters with theoriginal lamp); the new lamps need to know a global secret to be able todecrypt the network key which they receive from the parent luminaire. Inembodiments of the present disclosure on the other hand, opening thewireless network to the new replacement tube is not triggered by meansof remote control but rather based on detecting that one of the originalTLEDs is missing, and preferably also based on proximity detection ofnew replacement TLED.

Further, in embodiments of the present disclosure, then at theapplication level (not networking level) the behavior of three TLEDslocated in the same luminaire are united, while the three TLED tubes arestill part of a larger Zigbee network which comprises many luminaires(and hence many more TLEDs from other luminaires).

Also, in embodiments proximity between TLED tubes can be determined(e.g. with Touch Link) and it can be determined which luminaire (i.e.group of TLEDs) a replacement TLED is belonging; the replacement TLEDsubsequently joins the group. One particular embodiment for networkjoining is that the existing TLEDs open up the network using globalsecret to encrypted message with network key; this message is sent fromstill-alive TLED to the replacement TLED, so that replacement TLED canjoin the network

The proximity element also helps to enhance the security of networkjoining by replacement TLED. To restrict the communication to nodes inproximity, very low level of radio communication can be used (such as inTouchLink). Or as another example, the TLEDs may also have—next toZigbee radio—an additional iBeacon for assisting proximity location.

It will be appreciated that the above embodiments have been describedonly by way of example.

For instance, while in the above it has been described that one of theexisting lamps (e.g. the master) 12 a first detects a new lamp availableto join the network and in response is triggered to check whether one ofits cohabitants 12 b is missing from the same luminaire 4, this is notthe only option. Alternatively the checks could be performed the otherway around, so that when the existing (e.g. master) lamp 12 a detectsthat one of the other lamps from the same luminaire is missing, it thenscans for another, new lamp available to join the network. Or as anotheralternative both checks may be triggered together by a commissioningtool or a button on the TLED, following which the fully automatedprocess as described above occurs.

Further, the identifier that is used to collectively group together allthe lamps of the system into a wider group (as opposed to the subgroups)need not be a network-centric identifier. It will be appreciated that anID can be any unique identifier associated with the lamps or componentsof the network, and does not necessarily need to be an identifierassociated with the network per se (e.g. not necessarily the network IDof any particular protocol such as a ZigBee or Wi-Fi network ID). Forinstance, the collective ID for all the lamps (in the system inquestion) might be an identifier of a building or floor, or a GPScoordinate specifying a central or representative geographic location ofthe system or network. Similar comments apply to the subgroup ID, e.g.which can be but is not necessarily the ZigBee group address. Forinstance the subgroup ID could be an identifier of a floor or roomwithin a building, or a room within a floor. In such cases, thecollective identifier and/or subgroup ID might be sent as payload overthe network, so the network might be oblivious of the presence of theidentifier. In this case the collective identifier would not be anetwork ID, and/or the subgroup ID would not be the ZigBee groupaddress. To the network's MAC and PHY layer this identifier might benothing more than data. For all intents and purposes, the identifierstill is an address; but on a higher layer of abstraction.

Further, while the above has been described of the detecting and joiningbeing performed at the master lamps or “first component” (i.e. one ofthe existing, remaining components), this is not the only possibility.In alternative implementation, the “master” of “first” lamp 12 a doesnot have to be responsible for performing the network protocol requiredto join the new lamp to the network. Instead, the “master” of “first”lamp 12 a (or any of the remaining lamps 12 a, 12 b, 12 d) may broadcastthe fact that it is missing a lamp from its luminaire, and the new lampreceives these messages about the missing lamp(s). Thus the new lamp isable to detect a missing lamp from its respective luminaire vicariouslybased on a message from one (or more) of the other, existing lamps inthe same luminaire. The new lamp can then perform the necessary steps ofthe network protocol to join the network without further involvement ofthe existing lamp(s). Note that in this implementation, no step ofdetecting the new lamp is required (because it does not need to detectitself, and the other, existing lamps merely broadcast the message aboutthe missing lamp indiscriminately, not to an identified end point).

Further, the commissioning flow disclosed above can also be used withother protocols, not just ZigBee or ZigBee Light Link. Mostfundamentally the factory new mode is a mode in which a lamp 12 appearsas new to the commissioning tool 6, i.e. appears as awaitingcommissioning, and the non factory new mode is one in which the lamp 12does not appear as new to the commissioning tool 6. Other protocols mayhave or may be modified to incorporate a similar pair of modes, andcould also benefit by using the principle of artificially manipulatingthe factory new mode (or the like) to jointly represent lamps 12 a-d inthe same luminaire 4 as part of the commissioning process.

Further, in the above, it has been described that the master 12 adetects other lamps 12 b-12 d in the same luminaire 4 by signalling onthe ballast 10, then receiving the identifiers of those other lamps backvia another medium in the form of a wireless network (e.g. ZigBeenetwork). But alternatively, the slaves 12 b-d could instead respondback also via the ballast 10 (e.g. each sends its response at a randomtime, or using a carrier sense multiple access technique). Or as anotheralternative, the slaves 12 b-d could initially signal their identitiesto the master via the ballast 10 (without waiting for a signal from themaster first). Also, the protocol for determining which to lamp is tobecome the master could be implemented via other means, not just radiobeacons; e.g. via the ballast 10, or via coded light or ultrasound.Moreover, alternative protocols for selecting the master could be used:e.g. the master need not necessarily be the lamp with the lowestaddress, but could instead be the lamp with the highest address, or theaddress (or more generally ID) chosen according to some other rule. Orthe selection need not even be based on the address or identifier, andcould instead be based on some other attribute in the beacons, such as aseparate priority indicator in each beacon (such that the lamp with thehighest priority level becomes master).

Further, the commissioning flow is not limited to grouping lamps 12 a-din the same luminaire 4. More generally, the disclosed commissioningflow can also be used with other ways of determining the lamps 12 to begrouped, not just based on detecting whether in same luminaire 4. Forexample, other reasons to group lamps could include grouping clusters orzones of lamps within a room. In such cases, it is possible to arrangethe lamps 12 to each emit a signal such as a coded light signal, radiosignal or ultrasound signal comprising an identifier of the respectivelamp 12 (without that signal necessarily being hindered by therespective housing 14); and to arrange each of the lamps 12 to alsolisten for the signals from others of its neighbouring lamps in order tomeasure the received signal strength (e.g. RSSI) or time-of-flight(ToF). By collecting together these measurements (either at master oneof the lamps 12 or at a central device such as the commissioning tool 6or a lighting bridge), it is possible to detect the relative distancesbetween the different lamps 12 and thereby infer the topology of thelamps 12 in the environment 2, so as to detect which are to beconsidered in the same cluster.

Conversely, the disclosed techniques for detecting whether lamps are inthe same luminaire may be used with other commissioning flows, notnecessarily involving the manipulation of the factory new mode or thelike, or indeed in any other situation where it may be desired to detectthat lamps are the same luminaire 4 (e.g. for auditing purposes, or tocontrol as a group in an ad hoc manner without a specific commissioningphase).

Further, there are other possibilities for modulating the load, otherthan the on/off (in/out) approach shown in FIG. 7 whereby the switch M1is used to switch the load between either zero or the full load. E.g.alternatively, the LEDs 18 and/or driver 24 may stay connected incircuit and not be completely shorted, but a switchable or variableresistance or impedance may be included in series or in parallel withthe LEDs 18 and/or driver 24, and the microcontroller 46 may controlthis switchable or variable resistance or impedance in order to modulatethe load. Or more generally, other power line communication techniquesmay be available to a person skilled in the art. Moreover, the disclosedtechnique of modulating the power may be applied not just in the contextof a ballast 10, but any other power supply circuit, e.g. a circuitcomprising a transformer.

Note also for the avoidance of doubt that the term “wireless lamp” orsuch like, as used herein, refers to the fact that the lamp is able tocommunicate wirelessly, not that it does not need to be plugged in forpower. In general the wireless lamp may be powered by any means, such asby mains power or by a battery, e.g. a TLED tube may be powered by anemergency lighting battery housed within the luminaire.

Further, the term beacon in this application is not restricted to be aZigBee Beacon, but could also be any message which is sent outrepeatedly by the lamp, for instance a message looking for an opennetwork (or any message exposing an open network). Another alternativemethod is that the device will or will not respond to offers of opennetworks depending on its master/slave state. In this case, the lampsonly listen and do not send beacons per se. Rather, if the commissioningtool sends an offer of an open network, the master device will react tothe offer but slave device will ignore it.

Furthermore, note again that the scope of the present disclosure canalso extend to the commissioning of other components, not just lamps.Hence anywhere herein where there is mentioned a lamp, this may be moreread generally as a component. For example, increasingly people areusing wireless means such as ZigBee (etc.) to communicate between thecomponents even within a given luminaire. These components could includeany one or more of, e.g., a smoke detector component, a security camera,a driver for driving the luminaire's lamp(s), and/or a battery such asan emergency battery for powering the first lamp(s) (and/or othercomponents), or any of a variety of other possibilities. Any of theteachings herein could extend to the commissioning of a group ofcomponents comprising at least one lamp and one or more other types ofcomponents, e.g. to detect which components are in the same luminaire asthe lamp, with each of the components being configured in a similarmanner as the above-described lamps 12 a-12 d (at least as far as thecommissioning protocol goes).

Other variations to the disclosed embodiments can be understood andeffected by those skilled in the art in practicing the claimedinvention, from a study of the drawings, the disclosure, and theappended claims. In the claims, the word “comprising” does not excludeother elements or steps, and the indefinite article “a” or “an” does notexclude a plurality. A single processor or other unit may fulfil thefunctions of several items recited in the claims. The mere fact thatcertain measures are recited in mutually different dependent claims doesnot indicate that a combination of these measures cannot be used toadvantage. A computer program may be stored/distributed on a suitablemedium, such as an optical storage medium or a solid-state mediumsupplied together with or as part of other hardware, but may also bedistributed in other forms, such as via the Internet or other wired orwireless telecommunication systems. Any reference signs in the claimsshould not be construed as limiting the scope.

The invention claimed is:
 1. A system of replaceable componentscomprising a plurality of components connected in a wireless networkunder a collective ID, and at least one unconnected component availableto join the network, wherein the components are divided amongst aplurality of luminaires, each respective one of the luminairescomprising a respective subgroup of the components including at leastone lamp, and each of the subgroups having an individual respectivesubgroup ID identifying the respective subgroup, and wherein at least afirst one of the components is configured to automatically performoperations of: detecting whether a previously-present one of saidcomponents from the same respective one of said subgroups as the firstcomponent is missing from the network; and in response to the detectionthat the previously-present component is missing from the network,causing the unconnected component to be joined to the wireless networkunder said collective ID, and to be assigned to the same respectivesubgroup as the first component under the same respective subgroup ID,wherein the first component is one of said plurality of componentsalready connected in the network, and is configured to detect that theunconnected component is available to join the network, the firstcomponent being configured to perform said causing of the unconnectedcomponent to join the network in response to detecting that the newcomponent is available to join the network and detecting that thepreviously-present component is missing from the network, wherein thefirst component is further configured to detect whether the newcomponent is estimated to be within a predefined spatial proximity ofthe first component by checking whether a signal is received from thenew component via a constrained signaling channel whereby propagation ofthe signal is limited by a physical property of the luminaire, whereinif the signal is received the new component is determined to be withinsaid spatial proximity, at least said assigning of the new component tothe respective subgroup is performed on condition of detecting that thenew component is estimated to be within said spatial proximity, and saidphysical property of the respective luminaire comprises a power supplycircuit powering the components of the respective subgroup, and saidconstrained signaling channel is via modulation of a voltage and/orcurrent of the power supply circuit.
 2. The system of claim 1, whereinsaid causing of the new component to join the network, by the firstcomponent, is also conditional on the first component detecting that thenew component is estimated to be within said spatial proximity.
 3. Themethod of claim 1, wherein the first component is configured to performsaid detection of whether the new component is within said spatialproximity by: obtaining an indication of distance between the first lampand the new component based on a measurement of received signal strengthor time-of-flight of a signal emitted by the new component, anddetermining whether the new component is within said predeterminedproximity based on said indication.
 4. The method of claim 3, whereinthe signal is a visible light, invisible light, radio, heat, audio orultrasound signal.
 5. The method of claim 1, wherein the constrainedsignalling channel is via coded light, ultrasound and/or radio, and saidphysical property of the respective luminaire comprises at least part ofa housing of the luminaire which at least partially blocks thepropagation of the light, radio or ultrasound signal, the signalingchannel thereby being constrained.
 6. The method of claim 1, wherein thefirst component is configured to perform said detecting of the newcomponent by receiving a message from the new component via any of: asignal modulated into a voltage and/or current of a power supply circuitpowering the respective subgroup of components in the respectiveluminaire; or coded light, radio or ultrasound, or NFC.
 7. The method ofany of claim 1, wherein the first component is configured to performsaid detection that the previously-present component is missing byattempting to communicate with the previously-present component via anyof: modulation of a voltage and/or current of a power supply circuitpowering the respective subgroup of components in the respectiveluminaire; or coded light, radio, ultrasound or NFC.
 8. The system ofclaim 1, wherein the first component is a lamp.
 9. A first lamp for useas one of a system of replaceable components comprising a plurality ofcomponents connected in a wireless network, and at least one unconnectedcomponent available to join the network, wherein the components are tobe divided amongst a plurality of luminaires with each luminairecomprising a respective subgroup of the components including at leastone lamp and with each subgroup having a respective subgroup IDidentifying the respective subgroup within the network, and wherein thefirst lamp is configured to perform operations of: detecting anunconnected one of the components available to join the network;detecting whether a previously-present one of said components from thesame respective one of said subgroups as the first component is missingfrom the network; and in response to the detection that thepreviously-present component is missing from the network, causing theunconnected component to be joined to the wireless network under acollective ID, and to be assigned to the same respective subgroup as thefirst component under the same respective subgroup ID, wherein the firstcomponent is one of said plurality of components already connected inthe network, and is configured to detect that the unconnected componentis available to join the network, the first component being configuredto perform said causing of the unconnected component to join the networkin response to detecting that the new component is available to join thenetwork and detecting that the previously-present component is missingfrom the network, wherein the first component is further configured todetect whether the new component is estimated to be within a predefinedspatial proximity of the first component by checking whether a signal isreceived from the new component via a constrained signaling channelwhereby propagation of the signal is limited by a physical property ofthe luminaire, wherein if the signal is received the new component isdetermined to be within said spatial proximity, at least said assigningof the new component to the respective subgroup is performed oncondition of detecting that the new component is estimated to be withinsaid spatial proximity, and said physical property of the respectiveluminaire comprises a power supply circuit powering the components ofthe respective subgroup, and said constrained signaling channel is viamodulation of a voltage and/or current of the power supply circuit. 10.A non-transitory computer-readable medium comprising computer programproduct for operating a first component as one of a system ofreplaceable components comprising a plurality of components connected ina wireless network and at least one unconnected component available tojoin the network, wherein the components are to be divided amongst aplurality of luminaires with each luminaire comprising a respectivesubgroup of the components including at least one lamp and with eachsubgroup having a respective subgroup ID identifying the respectivesubgroup within the network, and wherein the computer-program productcomprises code configured so as when run on one or more processors inthe first component performs operations of: detecting whether apreviously-present one of said components from the same respective oneof said subgroups as the first component is missing from the network;and in response to the detection that the previously-present componentis missing from the network, causing the unconnected component to bejoined to the wireless network under a collective ID, and to be assignedto the same respective subgroup as the first component under the samerespective subgroup ID wherein the first component is one of saidplurality of components already connected in the network, and isconfigured to detect that the unconnected component is available to jointhe network, the first component being configured to perform saidcausing of the unconnected component to join the network in response todetecting that the new component is available to join the network anddetecting that the previously-present component is missing from thenetwork, wherein the first component is further configured to detectwhether the new component is estimated to be within a predefined spatialproximity of the first component by checking whether a signal isreceived from the new component via a constrained signaling channelwhereby propagation of the signal is limited by a physical property ofthe luminaire, wherein if the signal is received the new component isdetermined to be within said spatial proximity, at least said assigningof the new component to the respective subgroup is performed oncondition of detecting that the new component is estimated to be withinsaid spatial proximity, and said physical property of the respectiveluminaire comprises a power supply circuit powering the components ofthe respective subgroup, and said constrained signaling channel is viamodulation of a voltage and/or current of the power supply circuit. 11.A method performed in a system of replaceable components comprising aplurality of components connected in wireless a network, and at leastone unconnected component available to join the network, wherein thecomponents are divided amongst a plurality of luminaires, each luminairecomprising a respective subgroup of the components including at leastone lamp, and each subgroup having a respective subgroup ID, and whereinaccording to said method: a first one of the components automaticallydetects whether a previously-present one of said components in the samesubgroup as the first component is missing from the network; and inresponse to the detection that the previously-present component ismissing from the network, said first component automatically causes theunconnected component to be joined to the wireless network under acollective ID, and to be assigned to the same respective subgroup as thefirst component under the same respective subgroup ID wherein the firstcomponent is one of said plurality of components already connected inthe network, and is configured to detect that the unconnected componentis available to join the network, the first component being configuredto perform said causing of the unconnected component to join the networkin response to detecting that the new component is available to join thenetwork and detecting that the previously-present component is missingfrom the network, wherein the first component is further configured todetect whether the new component is estimated to be within a predefinedspatial proximity of the first component by checking whether a signal isreceived from the new component via a constrained signaling channelwhereby propagation of the signal is limited by a physical property ofthe luminaire, wherein if the signal is received the new component isdetermined to be within said spatial proximity, at least said assigningof the new component to the respective subgroup is performed oncondition of detecting that the new component is estimated to be withinsaid spatial proximity, and said physical property of the respectiveluminaire comprises a power supply circuit powering the components ofthe respective subgroup, and said constrained signaling channel is viamodulation of a voltage and/or current of the power supply circuit.